RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 858864 - create/ identify a mechanism for clients to determine that the pki subsystem is up
Summary: create/ identify a mechanism for clients to determine that the pki subsystem...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: pki-core
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Matthew Harmsen
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-19 20:56 UTC by Nathan Kinder
Modified: 2020-10-04 20:34 UTC (History)
3 users (show)

Fixed In Version: pki-core-9.0.3-26.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-21 10:05:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github dogtagpki pki issues 885 0 None closed create/ identify a mechanism for clients to determine that the pki subsystem is up 2020-10-04 20:34:07 UTC
Red Hat Product Errata RHSA-2013:0511 0 normal SHIPPED_LIVE Moderate: pki-core security, bug fix and enhancement update 2013-02-20 21:29:34 UTC

Description Nathan Kinder 2012-09-19 20:56:49 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/pki/ticket/314

IPA needs a way to determine that PKI is up and ready to service requests.  Checking the service status is not sufficient.
Comment 1 Ade Lee 2012-09-19 21:06:02 UTC 
Here is an initial idea to solve this:

1. There is a currently little used dogtag 9/10 servlet called getStatus.  This servlet returns the type of server (CA, KRA, etc) and the configuration status of the server (1 - configured / 0 - not configured).  

We can extend this servlet to provide other information like the dogtag version - which we need to know when supporting cloning between dogtag 9/10, and also whether the system is initialized.

In the init() function in CMSEngine.java, we can make the following changes:
1. at the beginning, set cs.startup_state in CS.cfg to "starting"
2. at the end, set cs.startup_state to "running"

The getStatus() servlet would query the cs.startup_state in CS.cfg.

If the server is down, you would not be able to reach that servlet in any case.
Comment 2 Ade Lee 2012-09-28 21:29:25 UTC 
Patch committed to IPA_v2_RHEL_6_ERRATA_BRANCH

commit b7acae7bf42d524355257d92bba9851fafc6f606
Author: Ade Lee <alee>
Date:   Fri Sep 28 17:27:12 2012 -0400

    Resolves #858864 - create/ identify a mechanism for clients to determine that the pki subsystem is up

commit f29ffc6392c758954fa53a0b4e645c0c72a636f4
Author: Ade Lee <alee>
Date:   Fri Sep 28 15:39:31 2012 -0400

    Resolves #858864 - create/ identify a mechanism for clients to determine that the pki subsystem is up
Comment 5 Namita Soman 2013-01-25 20:10:54 UTC 
Ran regression test suites for IPA, and didn't see any issues. So marking this verified.
Comment 6 errata-xmlrpc 2013-02-21 10:05:58 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0511.html
Note You need to log in before you can comment on or make changes to this bug.