If an error happens in SelfTestSubsystem initialization, the code will generate a generic error message without describing what's actually considered "invalid".
[22/Mar/2015:06:45:10][main]: CMS:Caught EBaseException The self test plugin named selftests.container.logger.class contains a value com.netscape.cms.logging.RollingLogFile which is invalid. at com.netscape.cmscore.selftests.SelfTestSubsystem.init(SelfTestSubsystem.java:1422) at com.netscape.cmscore.apps.CMSEngine.initSubsystem(CMSEngine.java:866) ...
Ideally the code should describe the error, throw the original exception, or chain the exception.
pki-edewata-0561-Fixed-generic-error-message-in-SelfTestSubsystem.patch pki-edewata-0561-Fixed-generic-error-message-in-SelfTestSubsystem.patch
Per CS/DS Meeting of 03/30/2015: Dogtag 9.0.x
This will help investigating selftest failures such as ticket #1697.
Fixed in master: 6a9990784b3a5ff18a800a288e8d1af173c7ae6e
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1302134
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: 10.3.0
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/1890
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.
Login to comment on this ticket.