Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
The ca.subsystem.certreq parameter is no longer reported missing
Previously, Identity Management (IdM) expected the *ca.subsystem.certreq* parameter to be defined in the `CS.cfg` public key infrastructure (PKI) configuration file. When starting the IdM server, an error occurred if *ca.subsystem.certreq* was missing. The error was not necessary because neither PKI nor IdM services use the parameter. To fix this problem, PKI code has been updated to ensure the parameter is only retrieved if it exists.
Description of problem:
at ipa startup, customer has the following error:
Restarting CA Service
Stopping pki-ca: waiting for processes 16466 to exit
killing 16466 which did not stop after 30 seconds [WARNING]
[ OK ]
Traceback (most recent call last):
File "/usr/sbin/pki-server", line 89, in <module>
cli.execute(sys.argv)
File "/usr/sbin/pki-server", line 84, in execute
super(PKIServerCLI, self).execute(args)
File "/usr/lib/python2.6/site-packages/pki/cli.py", line 195, in execute
module.execute(module_args)
File "/usr/lib/python2.6/site-packages/pki/server/cli/upgrade.py", line 103, in execute
scriptlet.execute()
File "/usr/lib/python2.6/site-packages/pki/server/upgrade/__init__.py", line 50, in execute
cert = self.subsystem.get_system_cert('subsystem')
File "/usr/lib/python2.6/site-packages/pki/server/__init__.py", line 93, in get_system_cert
cert['request'] = base64.b64decode(self.config['%s.%s.certreq' % (self.prefix, tag)])
KeyError: 'ca.subsystem.certreq'
Starting pki-ca: [ OK ]
Version-Release number of selected component (if applicable): pki-ca-9.0.3-45.el6_7.noarch
How reproducible: I don't know the root cause of why the value dissapear.
Steps to Reproduce: N/A
Expected results:
Additional info:
Fraser has found the workaround in freeipa alias
=========================================================
You can resolve the issue by stopping pki-cad, adding
'ca.subsystem.certreq=' (empty value) to CS.cfg, then restarting
pki-cad. AFAICT the absense of the certreq field will not cause any
problems.
I'm still investigating what caused the 'ca.subsystem.certreq'
config to disappear from CS.cfg in the first place.
===========================================================
thanks,
German.
Fix checked into rhel 6.8 branch ..
Counting objects: 62, done.
Compressing objects: 100% (31/31), done.
Writing objects: 100% (32/32), 5.18 KiB, done.
Total 32 (delta 18), reused 0 (delta 0)
To ssh://git.app.eng.bos.redhat.com/srv/git/pki.git
3637b1f..dd5039f DOGTAG_9_0_RHEL_BRANCH -> DOGTAG_9_0_RHEL_BRANCH
Matt will be creating builds.
This fix ensures that we only attempt to retrieve this parameter if it exists.
Currently, we make no use of this parameter - and if we need it later, we can retrieve it from the database.
So, if the parameter does not exist, no error should be seen.
I would suggest something like the following for doc text:
Occasionally, upon IPA server startup, an error would be encountered due to
a missing *ca.subsystem.certreq* parameter in the from PKI configuration
file 'CS.cfg'. Currently, since neither PKI nor IPA services utilize this
parameter, code has been added to PKI to ensure that this parameter is only
retrieved if it exists.
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.
https://rhn.redhat.com/errata/RHBA-2016-0909.html
Description of problem: at ipa startup, customer has the following error: Restarting CA Service Stopping pki-ca: waiting for processes 16466 to exit killing 16466 which did not stop after 30 seconds [WARNING] [ OK ] Traceback (most recent call last): File "/usr/sbin/pki-server", line 89, in <module> cli.execute(sys.argv) File "/usr/sbin/pki-server", line 84, in execute super(PKIServerCLI, self).execute(args) File "/usr/lib/python2.6/site-packages/pki/cli.py", line 195, in execute module.execute(module_args) File "/usr/lib/python2.6/site-packages/pki/server/cli/upgrade.py", line 103, in execute scriptlet.execute() File "/usr/lib/python2.6/site-packages/pki/server/upgrade/__init__.py", line 50, in execute cert = self.subsystem.get_system_cert('subsystem') File "/usr/lib/python2.6/site-packages/pki/server/__init__.py", line 93, in get_system_cert cert['request'] = base64.b64decode(self.config['%s.%s.certreq' % (self.prefix, tag)]) KeyError: 'ca.subsystem.certreq' Starting pki-ca: [ OK ] Version-Release number of selected component (if applicable): pki-ca-9.0.3-45.el6_7.noarch How reproducible: I don't know the root cause of why the value dissapear. Steps to Reproduce: N/A Expected results: Additional info: Fraser has found the workaround in freeipa alias ========================================================= You can resolve the issue by stopping pki-cad, adding 'ca.subsystem.certreq=' (empty value) to CS.cfg, then restarting pki-cad. AFAICT the absense of the certreq field will not cause any problems. I'm still investigating what caused the 'ca.subsystem.certreq' config to disappear from CS.cfg in the first place. =========================================================== thanks, German.