This man page improvement should be based upon information in:
Additionally, add the following information from Bugzilla Bug #1321491 - Clone installation fails with NullPointerException:
Installation of clones require nicknames to be given in the clone deployment file and the nicknames need to match the p12 file provided for pki_clone_pkcs12_path. For example, after adding the following nicknames to the clone deployment file, a cloned CA created successfully: * pki_ca_signing_nickname=casigningcert * pki_audit_signing_nickname=caauditsigningcert
I tried to reproduce the referenced bug but was unable to do so. Added comment to the bug and ticket. Not sure if anything is needed here.
NOTE: PKI TRAC Ticket #2313 - Deletion and again creation of client directory by subsystems. also references this bug, and this ticket is currently marked for 10.4.
Re-assigning this back to vakwetu, as I was never able to get to this ticket.
Per CS/DS Meeting of 08/08/2016: 10.3.6
Per PKI Bug Council of 02/09/2017: 10.3 => 10.4
Metadata Update from @mharmsen: - Issue assigned to vakwetu - Issue set to the milestone: 10.4
Metadata Update from @mharmsen: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None - Issue set to the milestone: 10.5 (was: 10.4)
Metadata Update from @mharmsen: - Issue priority set to: critical (was: major)
Metadata Update from @mharmsen: - Issue priority set to: major (was: critical)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
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/2481
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.