Bug 1588386 - Leaving IPA domain fails: Failed to remove krb5/LDAP configuration: expected str, bytes or os.PathLike object, not NoneType
Summary: Leaving IPA domain fails: Failed to remove krb5/LDAP configuration: expected ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: freeipa
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: IPA Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1609825
TreeView+ depends on / blocked
 
Reported: 2018-06-07 08:11 UTC by Martin Pitt
Modified: 2019-05-02 21:35 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
: 1609825 (view as bug list)
Environment:
Last Closed: 2019-05-02 21:35:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
ipaclient-uninstall.log (9.30 KB, text/plain)
2018-06-07 08:11 UTC, Martin Pitt
no flags Details
/var/log/ipaclient-install.log (112.26 KB, text/plain)
2018-06-07 08:12 UTC, Martin Pitt
no flags Details

Description Martin Pitt 2018-06-07 08:11:32 UTC
Created attachment 1448639 [details]
ipaclient-uninstall.log

Description of problem: When leaving a FreeIPA domain, this error happens:

Jun 07 04:02:20 x0.cockpit.lan realmd[1857]: Disabling client Kerberos and LDAP configurations
Jun 07 04:02:20 x0.cockpit.lan realmd[1857]: Failed to remove krb5/LDAP configuration: expected str, bytes or os.PathLike object, not NoneType
Jun 07 04:02:20 x0.cockpit.lan realmd[1857]: The ipa-client-install command failed. See /var/log/ipaclient-uninstall.log for more information
Jun 07 04:02:20 x0.cockpit.lan realmd[1857]: process exited: 2753
Jun 07 04:02:20 x0.cockpit.lan realmd[1857]:  ! Running ipa-client-install failed


Version-Release number of selected component (if applicable):

freeipa-client-4.6.90.pre2-3.fc28.x86_64
realmd-0.16.3-12.fc28.x86_64

How reproducible: Always

I attach the uninstall log.

Comment 1 Martin Pitt 2018-06-07 08:12:09 UTC
Created attachment 1448640 [details]
/var/log/ipaclient-install.log

For completeness, here is the corresponding install log.

Comment 2 Florence Blanc-Renaud 2018-06-11 11:17:55 UTC
Initial investigation: the uninstall log shows:
'/usr/bin/authselect', 'select', None, None, '--force'
when trying to revert to the pre-install state.
This means that it was unable to find in sysrestore the authselect profile + options that were configured on the system before ipa client was installed.

Need to investigate how this can happen and make it more robust (when unable to read the value, default to sssd profile with no options for instance).

Comment 3 Rob Crittenden 2018-07-30 14:50:41 UTC
Upstream ticket:
https://pagure.io/freeipa/issue/7657

Comment 6 Florence Blanc-Renaud 2018-09-19 12:12:28 UTC
Automation:
ipatests/test_integration/test_authselect.py::TestClientInstallation::test_uninstall_wrong_sysrestore

Comment 7 Ben Cotton 2019-05-02 20:54:29 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 8 Rob Crittenden 2019-05-02 21:35:24 UTC
Fixed in 4.7.2


Note You need to log in before you can comment on or make changes to this bug.