This ticket is basically a "clone" of pki-tomcat cannot be started after installation of ipa replica with ca which will be used to address the following issues not resolved by this ticket:
Tested out and verified that Thierry's fix for 389 TRAC Ticket #47721 - Schema Replication Issue allows us to keep the pki_clone_replicate_schema=True variable its original value of 'True'.
Re-tested with a 389 DS running with Thierry's replication patch.
This works (and I believe that it may have always worked but for a network glitch which silently altered my Clone CA machine's IP address) with the lone exception that the Administration certificate on the clone had to be manually installed even though the panel came up and allowed me to check the trust bits.
Consequently, I am moving this ticket back to NEEDS_TRIAGE, and reducing its priority from 'critical' back down to 'major'.
I would suggest that this ticket be moved to either the 10.2 backlog or 10.3 backlog since an easy work-around now exists.
Per CS/DS meeting of 4/7/2014, it was determined that this ticket would be filed for the 10.3 milestone.
Metadata Update from @mharmsen: - Issue set to the milestone: UNTRIAGED
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/1477
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.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.