Selftest ID: SystemCertsVerification for KRA is missing while running kra-selftest-run

[pki-bot]

This issue was migrated from Pagure Issue #2732. Originally filed by mharmsen (@mharmsen) on 2017-06-08 19:03:24:

• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1459245

---

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 : 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.

Steps to Reproduce:

1.stop KRA instance
2.Add selftests.container.order.onDemand=SystemCertsVerification:critical in
CS.cfg of KRA
3.start KRA instance.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-06-08 19:04:53

Per PKI Bug Council of 06/08/2017 - CLI for selftests is not yet supported - 10.5

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-06-08 19:04:53

Metadata Update from @mharmsen:

• Custom field component adjusted to General
• Custom field feature adjusted to ''
• Custom field origin adjusted to Community
• Custom field proposedmilestone adjusted to ''
• Custom field proposedpriority adjusted to ''
• Custom field reviewer adjusted to ''
• Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1459245
• Custom field type adjusted to defect
• Custom field version adjusted to ''
• Issue set to the milestone: 10.5

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-31 02:03:50

Metadata Update from @mharmsen:

• Issue priority set to: minor
• Issue set to the milestone: FUTURE (was: 10.5)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-05-02 18:35:49

Per 10.5.x/10.6 Triage: FUTURE

alee: broken CLI output most likely