Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1809492 - opendnssec package is missing /var/opendnssec/enforcer directory creation
Summary: opendnssec package is missing /var/opendnssec/enforcer directory creation
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: opendnssec
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Paul Wouters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-03 09:05 UTC by Florence Blanc-Renaud
Modified: 2022-07-01 16:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 17:18:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Florence Blanc-Renaud 2020-03-03 09:05:09 UTC
Description of problem:
Fedora 32 now ships opendnssec 2.1.6, and ipa-dns-install --dnssec-master is now failing with the following error:
Configuring OpenDNSSEC enforcer daemon (ods-enforcerd)
  [1/8]: checking status
  [2/8]: setting up configuration files
  [3/8]: setting up ownership and file mode bits
  [4/8]: generating master key
  [5/8]: setting up OpenDNSSEC
  [6/8]: setting up ipa-dnskeysyncd
  [7/8]: starting OpenDNSSEC enforcer
  [error] CalledProcessError: CalledProcessError(Command ['/bin/systemctl', 'restart', 'ods-enforcerd.service'] returned non-zero exit status 1: 'Job for ods-enforcerd.service failed because the control process exited with error code.\nSee "systemctl status ods-enforcerd.service" and "journalctl -xe" for details.\n')
Unexpected error - see /var/log/ipaserver-install.log for details:
CalledProcessError: CalledProcessError(Command ['/bin/systemctl', 'restart', 'ods-enforcerd.service'] returned non-zero exit status 1: 'Job for ods-enforcerd.service failed because the control process exited with error code.\nSee "systemctl status ods-enforcerd.service" and "journalctl -xe" for details.\n')

The journal logs:
ods-enforcerd[152206]: [file] chown() /var/opendnssec/enforcer failed: No such file or directory
ods-enforcerd[152206]: [engine] chdir to /var/opendnssec/enforcer failed: No such file or directory
ods-enforcerd[152206]: setup failed: Change directory failed
ods-enforcerd[152206]: [engine] enforcer shutdown
ods-enforcerd[152206]: [engine] enforcerd (pid: 152206) stopped with exitcode 3



Version-Release number of selected component (if applicable):
opendnssec-2.1.6-2.fc32.x86_64

How reproducible:
100%

Steps to Reproduce:
1. ipa-server-install without dns, then ipa-dns-install --dnssec-master --auto-forwarder -U


Actual results:
ipa-dns-install fails

Expected results:
ipa-dns-install should succeed

Additional info:
If I manually create /var/opendnssec/enforcer before running ipa-dns-install, installation succeeds.

Comment 1 Alexander Bokovoy 2020-03-03 09:28:06 UTC
PR: https://src.fedoraproject.org/rpms/opendnssec/pull-request/2

Comment 2 Fedora Update System 2020-03-03 14:55:06 UTC
FEDORA-2020-62c54952b9 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-62c54952b9

Comment 3 Fedora Update System 2020-03-03 16:10:36 UTC
opendnssec-2.1.6-3.fc32 has been pushed to the Fedora 32 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-62c54952b9

Comment 4 Fedora Update System 2020-03-04 20:14:04 UTC
freeipa-4.8.4-8.fc32, opendnssec-2.1.6-3.fc32 has been pushed to the Fedora 32 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-62c54952b9

Comment 5 Alexander Bokovoy 2020-03-09 12:39:43 UTC
Paul, one more issue, clean installation (no previous databases) produces the following issue:

  Installing       : opendnssec-2.1.6-3.fc33.x86_64                                                  228/277 
  Running scriptlet: opendnssec-2.1.6-3.fc33.x86_64                                                  228/277 
Slot 0 has a free/uninitialized token.
The token has been initialized and is reassigned to slot 441412172
*WARNING* This will erase all data in the database; are you sure? [y/N] Database setup successfully.
Error: no such table: rpm_migration
opendnssec 1.4 database found, migrating to 2.x
migrating conf.xml from 1.4 to 2.1 schema
Converting kasp.db
Error: no such table: dbadmin
chown: cannot access '/var/opendnssec/kasp.db': No such file or directory
/var/opendnssec/kasp.db conversion failed - not calling ods-migrate to complete migration. human intervention is needed

I think at the very least we need to fix chown and detection of the existing content.

Way to reproduce:

$ podman run -ti --hostname master.ipa.test f32/fedora-toolbox /sbin/init

(in a different terminal):
$ podman ps
CONTAINER ID  IMAGE                                                 COMMAND     CREATED         STATUS             PORTS  NAMES
0c1d6e190986  registry.fedoraproject.org/f32/fedora-toolbox:latest  /sbin/init  41 seconds ago  Up 40 seconds ago         blissful_wright
$ podman exec -ti blissful_write /bin/bash
[root@master ~]# sed -i s/gpgcheck=1/gpgcheck=0/g /etc/yum.repos.d/*.repo
[root@master ~]# dnf upgrade -y
[root@master ~]# dnf install -y freeipa-server-dns

Comment 6 Fedora Admin user for bugzilla script actions 2021-04-26 12:32:03 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 7 Fedora Program Management 2021-04-29 16:52:34 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2021-05-25 17:18:17 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 9 François Cami 2021-07-05 20:14:32 UTC
Re-opening.

Comment 10 Fedora Admin user for bugzilla script actions 2022-07-01 16:31:34 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.


Note You need to log in before you can comment on or make changes to this bug.