Jonathan wrote:
> James-
>
> I initially thought the same thing. Here's some steps to reproduce the
> issue:
>
> 1. Make a simple manifest, similar to the one below:
>
> user { "testy":
> ensure => present,
> uid => "2345",
> gid => "2345",
> groups => ["testy"],
> shell => "/bin/bash",
> home => "/tmp/poop",
> managehome => "true",
> }
>
> group {"testy":
> ensure => present,
> gid => 2345,
> }
>
> 2. Run puppet and ensure that the user and homedir have been created and
> check the permissions
> 3. Create a second directory anywhere on the filesystem, say /var/test
> 4. Open /etc/passwd and change the home dir for your test user to /
> 5. Open your test manifest and change the uid and gid of your test user
> to something else
> 6. Puppet changes the uid first, via usermod, so everything in / which
> was owned by the old uid is now owned by the new uid. Puppet changes the
> home dir after:
>
> notice: //User[testy]/uid: uid changed '12345' to '2345'
> notice: //User[testy]/home: home changed '/' to '/tmp/poop'
>
> You can verify by testing you second directory, wherever it may be.
>
> This can cause some very bad things to happen. Let me know if you need
> more info.
>
Jonathan
I understand the issue you're having... I just don't understand how your
fix can work - order of the properties in the type should have no impact
on how Puppet manages the resource.
Regards
James Turnbull
--
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
