When using kickstart to install a machine, I used an already
encrypted password. When it rebooted I couldn't log in as
root. After some investigating, I found out if I presented
the password hash I had specified in the kickstart file, it
would then let me log in.
In other words, during the install, the encrypted password
was encrypted again.
I checked the value of skipCrypt and found it to be 0 after the call
to poptGetContext inside of setRootPassword inside install2.c
This seems to be the problem, although why the poptGetContext is
returning skipCrypt as 0 is beyond me.
I have verified this on a test lab machine.
*** Bug 2627 has been marked as a duplicate of this bug. ***
When doing a kickstart installation with RedHat 6.0
(kickstart is great!) and writing something like
rootpw --iscrypted 8d78LWoez74ef
in the kickstart file sets the root password to "8d78LWoe".
--iscrypted still worked in 5.2. I quickly looked through
the code in install2, but there were little changes in
the password code, so I could not figure the problem out.
I have --useshadow in auth config.
*** This bug has been marked as a duplicate of 2880 ***
This issue is not resolved....I have downloaded the updated
bootnet.img and it is still doing the same thing. It is crypting
the iscrypted text
Yep, I can confirm this as well. The bootnet image dated
May 28th did not fix the problem.
Commit pushed to master at https://github.com/openshift/openshift-ansible
Merge pull request #2470 from abutcher/issue2460
[uninstall] Stop services on all hosts prior to removing files.