After successful pki instance installation it shows :
========================================================================== INSTALLATION SUMMARY ========================================================================== Administrator's username: kraadmin Administrator's PKCS #12 file: /opt/FoobarKRA_10.3.1/kra_admin_cert.p12 Administrator's certificate database: /opt/FoobarKRA_10.3.1/kra/alias To check the status of the subsystem: systemctl status pki-tomcatd@FoobarKRA_10.3.1.service To restart the subsystem: systemctl restart pki-tomcatd@FoobarKRA_10.3.1.service The URL for the subsystem is: https://cspki-vm2.englab.pnq.redhat.com:21443/kra PKI instances will be enabled upon system boot ==========================================================================
if we try to access "Administrator's certificate database" it says :
ls -al /opt/FoobarKRA_10.3.1/kra/alias ls: cannot access /opt/FoobarKRA_10.3.1/kra/alias: No such file or directory
if we check pkispawn logs :
<log snip> 'pki_backup_keys_p12': '/etc/pki/FoobarKRA_10.3.1/alias/kra_backup_keys.p12', 'pki_cert_database': '/etc/pki/FoobarKRA_10.3.1/alias/cert8.db', 'pki_client_cert_database': '/opt/FoobarKRA_10.3.1/kra/alias/cert8.db', 'pki_client_database_dir': '/opt/FoobarKRA_10.3.1/kra/alias', 'pki_client_key_database': '/opt/FoobarKRA_10.3.1/kra/alias/key3.db', 'pki_client_secmod_database': '/opt/FoobarKRA_10.3.1/kra/alias/secmod.db', 'pki_database_path': '/etc/pki/FoobarKRA_10.3.1/alias', 'pki_instance_database_link': '/var/lib/pki/FoobarKRA_10.3.1/alias', 'pki_key_database': '/etc/pki/FoobarKRA_10.3.1/alias/key3.db', 'pki_secmod_database': '/etc/pki/FoobarKRA_10.3.1/alias/secmod.db', 'pki_subsystem_database_link': '/var/lib/pki/FoobarKRA_10.3.1/kra/alias' </log snip>
It suggest that alias directory should exist as mentioned in "pki_client_database_dir" but it doesn't exist.
Steps to Reproduce:
1.Run pkispawn with attached file 2.refer and check installation details and logs 3.
Actual results:
No dir exist /opt/FoobarKRA_10.3.1/kra/alias
Expected results:
Ideally a dir /opt/FoobarKRA_10.3.1/kra/alias should be there with certtificate db
Additional info:
Refer attachment to get config file In associated bug: * Created attachment 1159872 config_template
Per PKI Bug Council of 06/23/2016: 10.4
Metadata Update from @gkapoor: - Issue set to the milestone: UNTRIAGED
Metadata Update from @mharmsen: - Custom field feature adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: None - Issue priority set to: minor (was: major) - Issue set to the milestone: 10.5 (was: UNTRIAGED)
Metadata Update from @mharmsen: - Custom field lowhangingfruit adjusted to vakwetu: X
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Per 10.5.x/10.6 Triage: 10.6
alee: trivial fix, but potentially confusing
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/2491
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.