Description of problem: If the "encrypted root password" checkbox is checked and then a kickstart is previewed, unchecking that checkbox cause --iscrypted to be included but the password is not encrypted. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Check "Encrypt root password" 2. Type a password into the Root Password/Confirm Password boxes 3. Click "File->Preview" 4. Uncheck "encrypt root password" 5. Click "File->Preview" Actual results: "rootpw --iscrypted UNENCRYPTED_PASSWORD" is generated in the kickstart file Expected results: "rootpw UNENCRYPTED_PASSWORD" should be generated in the kicktstart file. Additional info: The variable is simply never set back to False if it is set to true, included patch that should fix the problem.
Created attachment 154546 [details] Patch File
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Now I've read the whole message /usr/lib/python2.4/site-packages/pirut/GroupSelector.py:331... and I see that it's mainly pirut's problem. Right?
Correct, this would be a problem with the pirut component, which we pull in for packaging selection. It's possible I'm not setting something up right in s-c-kickstart, but I think we get this same message in anaconda so I'm leaning towards an internal pirut problem.
OK, thanks, I reported it piruts's maintainer. I guess we can wait come time for his opinion: https://bugzilla.redhat.com/show_bug.cgi?id=431580
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0343.html