Bug 1478366
Summary: | Crash noticed during IPA upgrade process due to ipa package. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Nikhil Dehadrai <ndehadra> |
Component: | ipa | Assignee: | IPA Maintainers <ipa-maint> |
Status: | CLOSED ERRATA | QA Contact: | ipa-qe <ipa-qe> |
Severity: | unspecified | Docs Contact: | Aneta Šteflová Petrová <apetrova> |
Priority: | unspecified | ||
Version: | 7.4 | CC: | frenaud, ftweedal, ksiddiqu, ndehadra, pasik, pvoborni, rcritten, slaznick, sumenon, tscherf |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ipa-4.6.4-1.el7 | Doc Type: | Known Issue |
Doc Text: |
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-30 10:56:00 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: |
Description
Nikhil Dehadrai
2017-08-04 12:46:58 UTC
Probably related to Custodia. Could you please provide /var/log/pki/pki-tomcat/ca/debug and also describe what is the impact? 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 Probably the related AVC mentioned (but the time is not the same) in bug 1478371 is: time->Fri Aug 4 09:14:59 2017 type=PROCTITLE msg=audit(1501852499.897:1007): proctitle=2F7573722F62696E2F707974686F6E32002F7573722F6C6962657865632F6970612F6970612D706B692D72657472696576652D6B65790063615369676E696E674365727420636572742D706B692D63612037353339353237612D306366372D346564372D626536322D323962373064613931323963006175746F2D68762D3031 type=SYSCALL msg=audit(1501852499.897:1007): arch=c000003e syscall=4 success=no exit=-13 a0=18267a0 a1=7ffee9b7f720 a2=7ffee9b7f720 a3=4 items=0 ppid=26998 pid=1626 auid=4294967295 uid=17 gid=17 euid=17 suid=17 fsuid=17 egid=17 sgid=17 fsgid=17 tty=(none) ses=4294967295 comm="ipa-pki-retriev" exe="/usr/bin/python2.7" subj=system_u:system_r:tomcat_t:s0 key=(null) type=AVC msg=audit(1501852499.897:1007): avc: denied { getattr } for pid=1626 comm="ipa-pki-retriev" path="/etc/openldap/certs" dev="dm-0" ino=100951062 scontext=system_u:system_r:tomcat_t:s0 tcontext=system_u:object_r:slapd_cert_t:s0 tclass=dir 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. Could you point us to time when this crash happen in relation to rpm upgrade process/ipa-server-upgrade? Or part of the beaker job where it happened? Upstream ticket for dealing specifically with the crashes: https://pagure.io/freeipa/issue/7115 Related Dogtag issue (regression in LWCA key replication): https://bugzilla.redhat.com/show_bug.cgi?id=1484359 Fixed upstream master: https://pagure.io/freeipa/c/09f746f56823ec6120437ba625f0db9b5d704e3e ipa-4-6: https://pagure.io/freeipa/c/f9074dcc9c025594d6961dcbb03805b9a20bb220 ipa-pki-retrieve-key should not be crashing anymore, although from the discussion I see that might have not been the root cause of the problem, so I am not setting this BZ to POST. If you think otherwise, you can change the status. Noticed similar crash during ipa-server upgrade process from : 1) RHEL 7.4-0day > RHEL 7.4 update2 2) RHEL 7.4 update1 > RHEL 7.4 update2 Crash is not seen while performing below upgrade path. 1. 7.4.z to 7.6 Sep 05 05:02:35 Installed: ipa-server-4.5.0-22.el7_4.x86_64 Sep 05 06:39:03 Updated: ipa-server-4.6.4-8.el7.x86_64 [root@master abrt]# pwd /var/spool/abrt [root@master abrt]# ls -l total 0 2. 7.5.z to 7.6 Sep 06 01:26:42 Installed: ipa-server-4.5.4-10.el7_5.4.3.x86_64 Sep 06 01:57:07 Updated: ipa-server-4.6.4-8.el7.x86_64 [root@master abrt]# pwd /var/spool/abrt [root@master abrt]# ls -l total 0 Hence marking the bug as VERIFIED. 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 |