Hide Forgot
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