Bug 1480502
Summary: | ipa server uninstall with -v option displays "IOError: [Errno 9] Bad file descriptor Logged from file ipautil.py, line 442" | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Sudhir Menon <sumenon> | ||||
Component: | ipa | Assignee: | IPA Maintainers <ipa-maint> | ||||
Status: | CLOSED ERRATA | QA Contact: | ipa-qe <ipa-qe> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 7.4 | CC: | cheimes, frenaud, lmiksik, ndehadra, pasik, pvoborni, rcritten, slaznick, tdudlak, tscherf | ||||
Target Milestone: | rc | Keywords: | Regression | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | ipa-4.6.4-7.el7 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | 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: | |||||||
Attachments: |
|
Description
Sudhir Menon
2017-08-11 09:27:58 UTC
ipa : DEBUG Removing service keytab: /etc/named.keytab ipa : DEBUG Removing service credentials cache ipa : DEBUG Starting external process ipa : DEBUG args=/usr/bin/kdestroy ipa : DEBUG Process finished, return code=0 ipa : DEBUG stdout= ipa : DEBUG stderr=Traceback (most recent call last): File "/usr/lib64/python2.7/logging/__init__.py", line 875, in emit self.flush() File "/usr/lib64/python2.7/logging/__init__.py", line 835, in flush self.stream.flush() IOError: [Errno 9] Bad file descriptor Logged from file ipautil.py, line 442 ipa : DEBUG runas=named (UID 25, GID 25) ipa : DEBUG Loading StateFile from '/var/lib/ipa/sysrestore/sysrestore.state' ipa : DEBUG Unconfiguring ipa-dnskeysyncd Was this already fixed upstream? This is fixed in FreeIPA master branch. A fix should arrive in RHEL 7.6 since the fix was a part of a major refactoring. Tested on Red Hat Enterprise Linux Server release 7.6 Beta (Maipo) using ipa-server-4.6.4-3.el7.x86_64 sssd-1.16.2-11.el7.x86_64 389-ds-base-1.3.8.4-9.el7.x86_64 krb5-server-1.15.1-34.el7.x86_64 pki-server-10.5.9-4.el7.noarch selinux-policy-3.13.1-211.el7.noarch Note: 1. There are certain traceback's which are yet to be addressed e.g as mentioned in comment#2 hence reopening the bug. ipaserver.install.installutils: DEBUG Removing service keytab: /etc/named.keytab ipaserver.install.installutils: DEBUG Removing service credentials cache ipapython.ipautil: DEBUG Starting external process ipapython.ipautil: DEBUG args=/usr/bin/kdestroy ipapython.ipautil: DEBUG Process finished, return code=0 ipapython.ipautil: DEBUG stdout= ipapython.ipautil: DEBUG stderr=Traceback (most recent call last): File "/usr/lib64/python2.7/logging/__init__.py", line 875, in emit self.flush() File "/usr/lib64/python2.7/logging/__init__.py", line 835, in flush self.stream.flush() IOError: [Errno 9] Bad file descriptor Logged from file ipautil.py, line 493 ipapython.ipautil: DEBUG runas=named (UID 25, GID 25) ---------------------------------- ipapython.ipautil: DEBUG stderr=Traceback (most recent call last): File "/usr/lib64/python2.7/logging/__init__.py", line 875, in emit self.flush() File "/usr/lib64/python2.7/logging/__init__.py", line 835, in flush self.stream.flush() IOError: [Errno 9] Bad file descriptor Logged from file ipautil.py, line 493 ipapython.ipautil: DEBUG runas=dirsrv (UID 994, GID 991) Created attachment 1473945 [details]
Uninstall Log
Removing the NOUPSTREAM label as the issue needs a new fix. Upstream ticket: https://pagure.io/freeipa/issue/7681 Fixed upstream master: https://pagure.io/freeipa/c/f0228fa6497f56200ce649c10d5619700bcc5fca https://pagure.io/freeipa/c/79fb0cc6634c7ab76e8181d1c55ac92a123142d8 Fixed upstream ipa-4-7: https://pagure.io/freeipa/c/cab3016e688a581b5cf56a06f7f13bc40ceb9f4f https://pagure.io/freeipa/c/2d2549d17704a430a344303c8de7c423e92f9d7f Fixed upstream ipa-4-6: https://pagure.io/freeipa/c/6b8b9b295454b37c1d14eaeee974b7993dccdf45 https://pagure.io/freeipa/c/306f34acd6940b31f2828d695d6e1d4742561873 Tested on Red Hat Enterprise Linux Server release 7.6 Beta (Maipo) using ipa-server-4.6.4-7.el7.x86_64 sssd-1.16.2-12.el7.x86_64 samba-4.8.3-4.el7.x86_64 389-ds-base-1.3.8.4-12.el7.x86_64 pki-server-10.5.9-6.el7.noarch ipa-client-4.6.4-7.el7.x86_64 Observations 1. IOError is no more seen. 2. traceback is also not seen at the end of uninstall log file. 3. For 'returned non-zero exit status 6!' bz1481949 has already been logged. ipapython.ipautil: DEBUG stderr=Removed symlink /etc/systemd/system/named.service. ipaserver.install.installutils: DEBUG Removing service keytab: /etc/named.keytab ipaserver.install.installutils: DEBUG Removing service credentials cache ipapython.ipautil: DEBUG Starting external process ipapython.ipautil: DEBUG args=/usr/bin/kdestroy ipapython.ipautil: DEBUG runas=named (UID 25, GID 25) ipapython.ipautil: DEBUG Process finished, return code=0 ipapython.ipautil: DEBUG stdout= ipapython.ipautil: DEBUG stderr= ipalib.install.sysrestore: DEBUG Loading StateFile from '/var/lib/ipa/sysrestore/sysrestore.state' ipaserver.install.service: DEBUG Unconfiguring ipa-dnskeysyncd Unconfiguring ipa-dnskeysyncd ipapython.ipautil: DEBUG stderr= ipaserver.install.installutils: DEBUG Removing service keytab: /etc/dirsrv/ds.keytab ipaserver.install.installutils: DEBUG Removing service credentials cache ipapython.ipautil: DEBUG Starting external process ipapython.ipautil: DEBUG args=/usr/bin/kdestroy ipapython.ipautil: DEBUG runas=dirsrv (UID 994, GID 990) ipapython.ipautil: DEBUG Process finished, return code=0 Systemwide CA database updated. Client uninstall complete. The ipa-client-install command was successful ipapython.ipautil: DEBUG Process finished, return code=0 ipapython.admintool: INFO The ipa-server-install command was successful 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 |