Hi and thanks for your response.
On Aug 15, 5:30 pm, Gary Larizza <[email protected]> wrote:
> There is an implicit relationship between managed users and groups in
> Puppet. If you're managing the group 'admin' and the user 'ringo' and ringo
> needs to be a part of the 'admin' group, Puppet will do the right thing.
Yet I was getting errors when creating users. Puppet was complaining
"Found dependency cycles in the following relationships", and listing
my users as depending on the "admin" group.
> Having said that - you want the 'gid' parameter as that will set the default
> group. 'groups' is an array of groups for which ringo is a member, but gid
> is what you want here. Give that a try and see if it works for you.
>
OK, this seems like the ticket, but not sure exactly what you mean.
In my "groups" module, should I set the gid explicitly like
class groups {
group { "admin":
ensure => present,
gid => 500,
}
}
and then in my users class:
class users {
user { 'ringo':
ensure => present,
uid => '1506',
gid => 500,
shell => '/bin/bash',
home => '/home/ringo',
managehome => true,
password => '$6$jomSNhWn
$AbuCjrUnLgmq5KfGygIcChHxM9Oxodcgv3ngHpbhJdJ4jzbsWt8Aj8aQI6G3WPqFe.mrG42KbD/',
}
}
?
The problem there is that I can't be sure whatever gid I choose won't
be taken on the client machine. (I am moving an existing cluster over
to puppet.)
Thanks again
Jim
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" 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-users?hl=en.
