Bug 1981850

Summary:	pki fails to start if empty dir /var/lib/pki/pki-tomcat/kra exists
Product:	[Fedora] Fedora	Reporter:	cdorney
Component:	pki-core	Assignee:	Chris Kelley <ckelley>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	34	CC:	aakkiang, abokovoy, alee, alexander.m.scheel, bugzilla-pkiqe, cfu, ckelley, edewata, jmagne, kwright, mharmsen, mkdineshprasanth
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1904112	Environment:
Last Closed:	2022-03-28 10:17:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1904112
Bug Blocks:

Description cdorney 2021-07-13 14:38:27 UTC

+++ This bug was initially created as a clone of Bug #1904112 +++

https://github.com/dogtagpki/pki/issues/3397

If an empty directory /var/lib/pki/pki-tomcat/kra is present on the filesystem, pki fails to start.

On fedora 32 with pki-server (10.10.0-2.fc32) :

# mkdir /var/lib/pki/pki-tomcat/kra
# systemctl restart pki-tomcatd@pki-tomcat
Job for pki-tomcatd failed because the control process exited with error code.
See "systemctl status pki-tomcatd" and "journalctl -xe" for details.

and the journal shows:

systemd[1]: Starting PKI Tomcat Server pki-tomcat...
pki-server[7658]: ERROR: [Errno 2] No such file or directory: '/var/lib/pki/pki-tomcat/kra/conf/CS.cfg'
systemd[1]: pki-tomcatd: Control process exited, code=exited, status=1/FAILURE
systemd[1]: pki-tomcatd: Failed with result 'exit-code'.
systemd[1]: Failed to start PKI Tomcat Server pki-tomcat.

pki should gracefully handle this situation and either consider kra not enabled or not installed.

Comment 1 cdorney 2021-07-23 14:54:21 UTC

PR Merged: https://github.com/dogtagpki/pki/pull/3666

Cherry-picked to v10.11: https://github.com/dogtagpki/pki/commit/1b18560bf05bfa54caea8d6e00fe285bf7d258e5

Comment 2 Ben Cotton 2021-11-04 13:49:52 UTC

This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2021-11-04 14:19:15 UTC

This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2021-11-04 15:17:00 UTC

This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Chris Kelley 2021-12-08 14:07:38 UTC

Assigning to myself as Ciarán has left the project.