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.
Description of problem:
With the method chosen to write the /etc/sysconfig/authconfig file it's
not possible to verify if the content has changed since the last run or
not due to the fact of using a dictionary to store the key/value params
and use iteritems over them.
a more reproduce able way is to instead of using iteritems from the dictionary a sorted list (see attached patch)
How reproducible:
as described above, everytime authconfig is called
this is what currently happens
$ md5sum /etc/sysconfig/authconfig
93adf3e2b9272626064870d1a7ac1ace /etc/sysconfig/authconfig
$ authconfig --updateall
$ md5sum /etc/sysconfig/authconfig
571a51f178bc49f7db03993255110f45 /etc/sysconfig/authconfig
$ authconfig --updateall
$ md5sum /etc/sysconfig/authconfig
6ac7ad67f313f8ce3250e8e56864b507 /etc/sysconfig/authconfig
this is what we are expecting
$ md5sum /etc/sysconfig/authconfig
93adf3e2b9272626064870d1a7ac1ace /etc/sysconfig/authconfig
$ authconfig --updateall
$ md5sum /etc/sysconfig/authconfig
93adf3e2b9272626064870d1a7ac1ace /etc/sysconfig/authconfig
Additional info:
there's an additional _truncate_ in the write section of the
SHVFile which also make's it impossible to have a unique hash when
deploying the plan file and afterwards calling "/usr/sbin/authconfig
--updateall"
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://rhn.redhat.com/errata/RHBA-2016-2462.html