dogtagpki

#2621 KRA subsystem went into a disabled state
Closed: duplicate Opened by mharmsen.

Closed: duplicate
Reopen Issue

We had to restart our HSM, this appears to have caused the KRA subsystem to go
into a disable state. This resulted into all future attempts to start
pki-tomcatd.target failing to deploy the KRA service.

After banging my head for an hour, we finally found the problem:

[root@kra01 ~]# pki-server subsystem-find

1 entries matched

Subsystem ID: kra
Instance ID: pki-tomcat
Enabled: False

Flipping this to enabled allowed a subsequent systemctl restart to bring up the
KRA service.

[root@kra01 ~]# pki-server subsystem-enable kra

Enabled "kra" subsystem

Subsystem ID: kra
Instance ID: pki-tomcat
Enabled: True

So the question is, why are we doing this in the first place? If there is an
error that caused the KRA to not deploy, it seems the correct behavior would be
to keep trying on subsequent service starts not to give up altogether.

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1432229

Metadata Update from @mharmsen:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1432229

Metadata Update from @mharmsen:
- Custom field component adjusted to General
- Custom field feature adjusted to ''
- Custom field origin adjusted to RHCust
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field type adjusted to defect
- Custom field version adjusted to ''

Metadata Update from @mharmsen:
- Issue set to the milestone: 0.0 NEEDS_TRIAGE (was: 10.4)

Metadata Update from @mharmsen:
- Issue priority set to: 3
- Issue set to the milestone: 10.4 (was: 0.0 NEEDS_TRIAGE)

This is fixed in ticket #2699. All subsystems are now reenabled on startup.

Metadata Update from @edewata:
- Issue close_status updated to: duplicate
- Issue set to the milestone: 10.4.6 (was: 10.4)
- 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/2741

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
None
Normal
defect
''
''
RHCust
''
''
General
''
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.