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 1454471 - Enabling all subsystems on startup
Summary: Enabling all subsystems on startup
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Endi Sukma Dewata
QA Contact: Asha Akkiangady
Petr Bokoc
: 1432229 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2017-05-22 20:26 UTC by Matthew Harmsen
Modified: 2020-10-04 21:30 UTC (History)
12 users (show)

Fixed In Version: pki-core-10.4.1-7.el7
Doc Type: Bug Fix
Doc Text:
PKI subsystems which failed self tests are now automatically re-enabled on startup Previously, if a PKI subsystem failed to start due to self test failure, it was automatically disabled to prevent it from running in an inconsistent state. The administrator was expected to re-enable the subsystem manually using "pki-server subsystem-enable" after fixing the problem. However, this was not clearly communicated, potentially causing confusion among administrators who were not always aware of this requirement. To alleviate this problem, all PKI subsystems are now re-enabled automatically on startup by default. If a self-test fails, the subsystem is disabled as before, but it will no longer require manual re-enabling. This behavior is controlled by a new boolean option in the `/etc/pki/pki.conf` file, `PKI_SERVER_AUTO_ENABLE_SUBSYSTEMS`.
Clone Of:
Last Closed: 2017-08-01 22:52:53 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github dogtagpki pki issues 2819 0 None None None 2020-10-04 21:30:09 UTC
Red Hat Product Errata RHBA-2017:2110 0 normal SHIPPED_LIVE pki-core bug fix and enhancement update 2017-08-01 19:36:59 UTC

Description Matthew Harmsen 2017-05-22 20:26:58 UTC
This bug is created as a clone of upstream ticket:

Currently if selftest fails during startup the subsystem will undeploy (i.e. disable) itself to prevent partially running service which could confuse other services that depend on it.

The admin is expected to investigate and fix the failure, then reenable the subsystem manually with this command (see http://pki.fedoraproject.org/wiki/SelfTest):

    $ pki-server subsystem-enable ca

The selftest error and the instruction to reenable the subsystem is written into the log, but often times the admin does not notice that immediately, leading to confusions.

One possible solution is to automatically reenable all subsystems on Tomcat restart. If the selftest is still failing the subsystem will shut itself down as before, but at least the admin is no longer required to reenable the subsystem manually.

Comment 2 Endi Sukma Dewata 2017-05-23 19:33:37 UTC
Fixed in master:
* https://github.com/dogtagpki/pki/commit/8016ed7972d9211e7f0db14e45bc9658a7b292ef

Comment 3 Endi Sukma Dewata 2017-05-25 14:42:52 UTC
FYI, the auto-enable behavior can be configured using the PKI_SERVER_AUTO_ENABLE_SUBSYSTEMS property in pki.conf. See http://pki.fedoraproject.org/wiki/SelfTest

Comment 4 Endi Sukma Dewata 2017-05-30 15:02:20 UTC
*** Bug 1432229 has been marked as a duplicate of this bug. ***

Comment 6 Sumedh Sidhaye 2017-06-24 10:16:48 UTC
[root@csqa4-guest01 hsm_setup]# rpm -qi pki-server
Name        : pki-server
Version     : 10.4.1
Release     : 10.el7
Architecture: noarch
Install Date: Friday 23 June 2017 12:09:25 AM EDT
Group       : System Environment/Base
Size        : 4634270
License     : GPLv2
Signature   : (none)
Source RPM  : pki-core-10.4.1-10.el7.src.rpm
Build Date  : Tuesday 20 June 2017 01:23:22 AM EDT
Build Host  : ppc-046.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor      : Red Hat, Inc.
URL         : http://pki.fedoraproject.org/
Summary     : Certificate System - PKI Server Framework

After setting PKI_SERVER_AUTO_ENABLE_SUBSYSTEMS=True in /etc/pki/pki.conf the subsystem is not disabled, when the selftests fail the subsystem is simply shutdown instead of being disabled.

Comment 7 errata-xmlrpc 2017-08-01 22:52:53 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.


Note You need to log in before you can comment on or make changes to this bug.