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.
DescriptionJenny Severance
2010-06-16 14:39:18 UTC
Description of problem:
[root@jennyv2 ~]# /usr/sbin/authconfig --disableldap --disablekrb5
--disablesssd --disablesssdauth --disablemkhomedir --update
Traceback (most recent call last):
File "/usr/sbin/authconfig", line 894, in <module>
sys.exit(module.run())
File "/usr/sbin/authconfig", line 478, in run
self.readAuthInfo()
File "/usr/sbin/authconfig", line 329, in readAuthInfo
self.info = authinfo.read(self.printError)
File "/usr/share/authconfig/authinfo.py", line 922, in read
info.read()
File "/usr/share/authconfig/authinfo.py", line 2174, in read
self.readSSSD()
File "/usr/share/authconfig/authinfo.py", line 1531, in readSSSD
domain = self.sssdConfig.get_domain(domname)
File "/usr/lib/python2.6/site-packages/SSSDConfig.py", line 1456, in
get_domain
if (opt['name'], opt['value']) not in providers]
File "/usr/lib/python2.6/site-packages/SSSDConfig.py", line 888, in
set_option
(self.name, option))
SSSDConfig.NoOptionError: Section [ldap] has no option [mid_id]
Version-Release number of selected component (if applicable):
authconfig-6.1.4-4.el6.i686
How reproducible:
always
Steps to Reproduce:
1. setup up legacy (no sssd) ldap and krb5 network authentication
2. /usr/sbin/authconfig --disableldap --disablekrb5 --disablesssd --disablesssdauth --disablemkhomedir --update
Actual results:
track back
Expected results:
helpful error that tells explains that sssd is not enable and what to do.
Additional info:
Comment 2RHEL Program Management
2010-06-16 14:52:59 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
Hmm, that looks like a somehow corrupted sssd configuration is parsed by the SSSDConfig and it gives a traceback.
Should this really be handled in authconfig and not in the SSSDConfig API?
Steve, what do you think?
Comment 4Stephen Gallagher
2010-06-16 15:11:06 UTC
Well, normally this wouldn't be an issue, except that 'mid_id' is a typo that's not recognized by the SSSDConfig API, which means that this traceback is perfectly valid.
In the case when SSSD was not ever configured but the command above is ran the authcofig should detect that SSSD not configured and not blow up but return success. This is what this bug is about.
Dmitri, but this is not how the authconfig works. It tries to read configurations of all possible services because they might be later switched on - in the GUI.
The problem is that the NoOptionError is not mentioned here for the get_domain call: https://fedorahosted.org/sssd/wiki/SSSDPythonConfigApi/SSSDConfig#get_domainname
Stephen, how should I handle the traceback and what happens later when I try to write into such misconfigured config file?
I think the config API should ignore such errors and then overwrite if such domain is saved later.
Comment 8Stephen Gallagher
2010-06-16 15:52:01 UTC
Tomas: yeah, that actually is a bug in get_domainname(). I should be trapping that.
Comment 9Stephen Gallagher
2010-06-16 16:17:55 UTC
Tomas and I discussed this elsewhere. I will update the get_domain() function to handle unknown options and silently drop them from the configuration. There's no sense in holding onto invalid options anyway.
Comment 11Stephen Gallagher
2010-06-16 17:23:00 UTC
*** Bug 604699 has been marked as a duplicate of this bug. ***
Comment 12Stephen Gallagher
2010-06-16 17:28:19 UTC
*** Bug 559004 has been marked as a duplicate of this bug. ***
Comment 14Gowrishankar Rajaiyan
2010-07-27 13:29:48 UTC
Disabling SSSD using authconfig even when its not configured returns success.
Verified. Version: sssd-1.2.1-21.
Comment 15releng-rhel@redhat.com
2010-11-10 21:39:57 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Description of problem: [root@jennyv2 ~]# /usr/sbin/authconfig --disableldap --disablekrb5 --disablesssd --disablesssdauth --disablemkhomedir --update Traceback (most recent call last): File "/usr/sbin/authconfig", line 894, in <module> sys.exit(module.run()) File "/usr/sbin/authconfig", line 478, in run self.readAuthInfo() File "/usr/sbin/authconfig", line 329, in readAuthInfo self.info = authinfo.read(self.printError) File "/usr/share/authconfig/authinfo.py", line 922, in read info.read() File "/usr/share/authconfig/authinfo.py", line 2174, in read self.readSSSD() File "/usr/share/authconfig/authinfo.py", line 1531, in readSSSD domain = self.sssdConfig.get_domain(domname) File "/usr/lib/python2.6/site-packages/SSSDConfig.py", line 1456, in get_domain if (opt['name'], opt['value']) not in providers] File "/usr/lib/python2.6/site-packages/SSSDConfig.py", line 888, in set_option (self.name, option)) SSSDConfig.NoOptionError: Section [ldap] has no option [mid_id] Version-Release number of selected component (if applicable): authconfig-6.1.4-4.el6.i686 How reproducible: always Steps to Reproduce: 1. setup up legacy (no sssd) ldap and krb5 network authentication 2. /usr/sbin/authconfig --disableldap --disablekrb5 --disablesssd --disablesssdauth --disablemkhomedir --update Actual results: track back Expected results: helpful error that tells explains that sssd is not enable and what to do. Additional info: