The following CERT_REQUEST_PROCESSED events seem to have incorrect outcomes.
These successes probably should have been failures:
These failures probably should have been successes:
Per discussion with cfu and alee, the CERT_REQUEST_PROCESSED's outcome can be interpreted in two ways:
Success means that the request has been processed, but the certificate may or may not be issued, depending on approval or rejection. Failure means that there is a problem so the request cannot be processed.
Success means the request is approved so the certificate is issued. Failure means that the certificate is not issued due to rejection or other problems.
The definition of the outcome needs to be clarified first, then the code needs to be fixed accordingly.
See also ticket #2663 and #2690.
Metadata Update from @edewata: - 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 type adjusted to None - Custom field version adjusted to None
Metadata Update from @mharmsen: - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Metadata Update from @mharmsen: - Custom field proposedmilestone adjusted to 10.5 (was: None) - Custom field proposedpriority adjusted to critical (was: None)
Metadata Update from @mharmsen: - Issue assigned to edewata
Per meeting of 20171113 - 10.5 - critical
Metadata Update from @mharmsen: - Issue priority set to: critical - Issue set to the milestone: 10.5 (was: 0.0 NEEDS_TRIAGE)
Metadata Update from @mharmsen: - Custom field proposedmilestone adjusted to None (was: 10.5)
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1539198
Fixed in master:
Fixed in 10.5 branch:
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5.5 (was: 10.5)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.5.5-1.fc27
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/2958
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.