Open pki-bot opened 3 years ago
Comment from mharmsen (@mharmsen) at 2017-06-08 18:57:46
Metadata Update from @mharmsen:
Comment from mharmsen (@mharmsen) at 2017-06-08 19:00:54
Per PKI Bug Council of 06/08/2017 - CLI for selftests is not yet supported - 10.5
Comment from mharmsen (@mharmsen) at 2017-08-31 02:02:42
Metadata Update from @mharmsen:
Comment from mharmsen (@mharmsen) at 2018-05-02 18:34:12
Per 10.5.x/10.6 Triage: FUTURE
alee: usability issue. should not be too hard to fix.
This issue was migrated from Pagure Issue #2731. Originally filed by mharmsen (@mharmsen) on 2017-06-08 18:56:53:
This bug is raised so as to improve failures while selftest is happened for subsystems so that cli can handle it gracefully.
Test case 1 :
If a selftestID doesn't exist, so still it gives the status.Ideally it should exit with not a valid id.
[root@pki1 test_dir]# pki -p 25080 -d /opt/rhqa_pki/certdb/ -c Secret123 -n "TPS_AdminV" tps-selftest-show testing
SelfTest "testing"
SelfTest ID: testing Enabled at startup: false Enabled on demand: false
Test Case 2:
In case self test is failed to run,It gives NPE in debug logs.
Steps to reproduce:
selftests.container.instance.OCSPPresence=com.netscape.cms.selftests.ocsp.OCSP
Presence
selftests.container.order.onDemand=OCSPPresence:critical,
SystemCertsVerification:critical, OCSPValidity:critical
selftests.container.order.startup=OCSPPresence:critical,
SystemCertsVerification:critical
selftests.plugin.OCSPPresence.OcspSubId=ocsp
Additional info: