Closed Bug 1344275 Opened 7 years ago Closed 7 years ago

Can't login to root on new ubuntu 16.04 kickstart install

Categories

(Infrastructure & Operations :: RelOps: Puppet, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dividehex, Assigned: dividehex)

References

Details

We have traditionally set the root password during kickstart (aka kickstart password).  This allows for logging in to troubleshoot a host that has fallen between the kickstart and puppetizing process.

Currently, the kickstart process completes it run (including the %post script) but the rootpw --iscrypted part doesn't seem to have any effect.

I was able to confirm this by inspecting /etc/shadow during the kickstart %post.
I've made a mistake here.  Upon further inspect, the password is being set AFTER the %post script is executed.  I noticed this after I booted the systemrescue image and mounted /dev/sda1.   I just don't understand why the kickstart password wasn't working for me.  Manually altering the /etc/shadow allowed me to get past this issue for the time being and start getting to the root causes of why the host installs completely but doesn't puppetize.  (See Bug 1344720 for juicy details)

I should probably double check that our kickstart password matches up with the hash being used.  Maybe it is a good time to change that anyway.
Summary: Root password not set during Ubuntu 16.04 kickstart → Can't login to root on new ubuntu 16.04 kickstart install
Kickstart password has been updated.  New password added to releng gpg kickstart.txt
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Blocks: 1366828
You need to log in before you can comment on or make changes to this bug.