ipa-server-install uses systemctl start pki-tomcatd.target It appears that pki is not doing a systemctl daemon-reload after adding the /etc/systemd/system/pki-tomcatd.target.wants/pki-tomcatd@pki-tomcat.service symlink.
Before doing systemctl daemon-reload
systemctl start pki-tomcatd.target - does nothing
after doing systemctl daemon-reload
systemctl start pki-tomcatd.target - starts pki
In 389, the 389 install code (DSCreate.pm) calls systemctl daemon-reload after creating the service symlink
Note: this prevents install of ipa on F19.
Workaround 1: while ipa-server-install is running, do systemctl daemon-reload repeatedly during the certsys install phase
Workaround 2: run ipa-server-install in pdb - break at ipapython/platform/base/systemd.py - start() - call systemctl daemon-reload before invoking systemctl start
DOGTAG_10_0_BRANCH:
DOGTAG_10_1_BRANCH:
master
Metadata Update from @rmeggins: - Issue set to the milestone: 10.0.7
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1436
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.