dogtagpki

#643 Make sure pkispawn/pkidestroy returns the correct code
Closed: fixed Opened by edewata.

Closed: fixed
Reopen Issue

There isn't a known issue yet, but we should check the code to ensure that pkispawn/pkidestroy returns 0 on success and non-zero number on failures.

[06/04/2014] - Moving to Milestone 10.2.3 due to schedule restrictions.

proposed Milestone: 10.2.3 - Per Dogtag 10.2.3 meeting of 09/25/2014

Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.3

Metadata Update from @edewata:
- Issue assigned to mharmsen
- Issue set to the milestone: UNTRIAGED

Currently all exceptions in pkispawn/pkidestroy will generate a non-zero return code.

Metadata Update from @edewata:
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: fixed
- Issue set to the milestone: 10.6.0 (was: UNTRIAGED)
- Issue status updated to: Closed (was: Open)

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/1213

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.
Metadata
None
None
None
Normal
None
None
None
None
task
Installation/Configuration
Installer Cleanup/ Improvement
Community
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.