During the testing of [Dogtag TRAC Ticket #840 - pkispawn requires policycoreutils-python], we discovered some issues related to schema replication, and filed https://fedorahosted.org/389/ticket/47721 389 TRAC Ticket #47721 - Schema Replication Issue.
Since this issue was discovered by merely cloning a Dogtag 10.1 (Fedora 20) CA from a Dogtag 10.0 (Fedora 19) Master CA, it was also determined that IPA replication did not suffer from this issue.
Further investigation yielded the observation that if the following '/etc/pki/default.cfg' variable:
... [Tomcat] ... pki_clone_replicate_schema=True ...
was overridden (e. g. - in a 'pkispawn' configuration file):
... [Tomcat] pki_clone_replicate_schema=False ...
Dogtag would avoid this pitfall, and execute successfully.
Although correction of the aforementioned 389 issue may resolve this issue, this ticket has been filed for the Dogtag Team to consider changing the default value of the 'pki_clone_replicate_schema' parameter from 'True' to 'False'.
[06/04/2014] - Moving to Milestone 10.2 (July).
This ticket blocks PKI TRAC Ticket #1076 - Man Page Bugs: pkispawn, as it may be necessary to reflect any changes in the 'pkispawn' man page.
We have chosen to close this bug as 'wont fix' due to the fact that the following ticket has been resolved:
Metadata Update from @mharmsen: - Issue assigned to mharmsen - Issue set to the milestone: 10.2 - 07/14 (July)
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/1437
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.