Description of problem:
$ pki -p 21080 -d /opt/rhqa_pki/certdb/ -c Secret123 -n "KRA_AdminV" kra-selftest-run Selftest ID: KRAPresence Status: PASSED ------------------- Selftests completed -------------------
Self test for KRA on demand always run only KRAPresence.For other subsystems it always run for Selftest ID: SystemCertsVerification.
Not sure if it is needed.I tried setting selftests.container.order.onDemand=SystemCertsVerification:critical in CS.cfg. After that it gives :
selftests.container.order.onDemand=SystemCertsVerification:critical
$ pki -p 21080 -d /opt/rhqa_pki/certdb/ -c Secret123 -n "KRA_AdminR" kra-selftest-find ----------------- 2 entries matched ----------------- SelfTest ID: KRAPresence Enabled at startup: false Enabled on demand: false SelfTest ID: SystemCertsVerification Enabled at startup: true Critical at startup: true Enabled on demand: true Critical on demand: true ---------------------------- Number of entries returned 2 ----------------------------
and it is start a selftest-run using:
[root@pki1 ocsp]# pki -p 21080 -d /opt/rhqa_pki/certdb/ -c Secret123 -n "KRA_AdminR" kra-selftest-run Selftest ID: SystemCertsVerification Status: PASSED ------------------- Selftests completed -------------------
It doesn't show KRAPresence.
This behavior deviates from other cli behavior.
Version-Release number of selected component (if applicable): pki-ca-10.4.1-8.el7.noarch
How reproducible: always
Steps to Reproduce: 1.stop KRA instance 2.Add selftests.container.order.onDemand=SystemCertsVerification:critical in CS.cfg of KRA 3.start KRA instance.
CS.cfg
Actual results:
Expected results:
Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1459245
Metadata Update from @cipherboy: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1459245 - Custom field type adjusted to None - Custom field version adjusted to None
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/3273
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.