-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Yesterday, `nscd` on one of our Puppet nodes lost its frakking mind > and decided there were no users on the box. Puppet comes along, > looking to make sure the comment for root has the correct value, and > sees that there’s no such user… so it adds it. I don’t know the exact > command Puppet used (since it didn’t fail) but either `useradd` or > `usermod` was somehow aware of the next available UID and that root > already existed, so root had its UID (and home directory) changed.
if you look into the provider code, you'll see that it uses useradd, BUT afair puppet tries to predict the next available UID for you and passes that to useradd as well. This might be the reason that it was successfull as useradd didn't choke, hence puppet ran successful. In general there are some parts of a system which I still fear to touch automatically. The root user is one of the last remaining parts, but as Jonathan mentioned, setting uid => 0, might have helped. cheers pete -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxFyL0ACgkQbwltcAfKi39IJgCaAjDfgA8uUibXbzpcpp0Nc8Ef 3WUAn3KBeoOiUPpXLqrUOjHh2ex83mz8 =fkMT -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
