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.
A crash is reported after an unsuccessful lightweight CA key retrieval
When using Identity Management (IdM), if retrieving the lightweight certificate authority (CA) key fails for some reason, the operation terminates unexpectedly with an uncaught exception. The exception results in a crash report.
Hi Fraseer / Petr,
As far as impact is considered, not entirely sure at this point of time. Also another thing to note here is the crash is noticed before upgrade is run.
Please find attached debug log as requested. I also noticed avc's during this run for which I have already logged bz1478371, if that helps.
Let me know, if you need anymore information
It looks like the ipa-pki-retrieve-key program is crashing due to the
ipa-custodia server returning non-200 response.
This isn't really a problem, there are a variety of conditions that can
cause this e.g. LDAP server being temporarily down (as in the above
case).
IMO it is not a serious issue; the "fix" is to catch all exceptions and
exit cleanly with nonzero exit status instead of allowing the
interpreter to crash with uncaught exception.
Fraser, do we know when ipa-pki-retrieve-key was called and if it was OK/expected for it to fail? I.e. are we sure that it doesn't break any functionality.
It was called to replicate lightweight CA signing keys. Without knowing
more about the history of the topology in question it's impossible to say
whether the invocation of the ipa-pki-retrieve-key is expected or not,
or the root cause as to why key retrieval is not succeeding.
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://access.redhat.com/errata/RHBA-2018:3187
Description of problem: While upgrading IPA server from RHEL 7.4(4.5.0.21) to RHEL 7.4.1(4.5.0-21.el7_4.1), found crash report related to package ipa-server-4.5.0-21.el7. Full Backtrace: models.py:834:raise_for_status:HTTPError: 401 Client Error: Unauthorized Traceback (most recent call last): File "/usr/libexec/ipa/ipa-pki-retrieve-key", line 32, in <module> print(client.fetch_key(keyname, store=False)) File "/usr/lib/python2.7/site-packages/ipaserver/secrets/client.py", line 101, in fetch_key r.raise_for_status() File "/usr/lib/python2.7/site-packages/requests/models.py", line 834, in raise_for_status raise HTTPError(http_error_msg, response=self) HTTPError: 401 Client Error: Unauthorized Local variables in innermost frame: self: <Response [401]> http_error_msg: '401 Client Error: Unauthorized' Additional information: environ: :USE_NUXWDOG=false :JAVA_OPTS=-DRESTEASY_LIB=/usr/share/java/resteasy-base -Djava.library.path=/usr/lib64/nuxwdog-jni :LOGNAME=pkiuser :USER=pkiuser :TOMCAT7_USER=pkiuser :TOMCAT_LOG=/var/log/pki/pki-tomcat/tomcat-initd.log :CATALINA_HOME=/usr/share/tomcat :LANG=en_US.UTF-8 :SHELL=/sbin/nologin :CATALINA_TMPDIR=/var/lib/pki/pki-tomcat/temp :SHLVL=0 :NSS_ENABLE_PKIX_VERIFY=1 :TOMCAT7_SECURITY=true :JAVA_HOME=/usr/lib/jvm/jre-1.8.0-openjdk :HOME=/usr/share/pki :TOMCATS_BASE=/var/lib/tomcats/ :PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin :TOMCAT_USER=pkiuser :NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat :SECURITY_MANAGER=true :NAME=pki-tomcat :TOMCAT_CFG_LOADED=1 :OLDPWD=/ :CATALINA_PID=/var/run/pki/tomcat/pki-tomcat.pid :CATALINA_BASE=/var/lib/pki/pki-tomcat :PWD=/usr/share/tomcat :PKI_VERSION=10.4.1 :XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt