date:20110620

[Puppet Users] Re: Facter + storeconfigs missing fact_values

2011-06-20 Thread josbal

I have added a simple notify check into our manifest for the offending
fact. If the value is set to expected it print a message into the
puppet log, however the nodes that aren't storing this fact in
database also are processing this conditional in the manifest as
expected.

Further more i have run puppet in debug on some of the nodes with this
issue, but there is no report attempting to process the condition,
even though i can see that require fact file is loaded at the start of
the run.

As a last resort i removed the state dir to force the client to
download the catalogue again and this seems to have forced both the
correct running of the conditional statement and the loading of the
fact value into the storeconfig database.

I shall refresh the state of all my nodes and see if this clears the
issue.

On Jun 20, 1:24 pm, Patrick Mohr kc7...@gmail.com wrote:
 Well, it would help if you can find out if the problem is with storeconfigs
 of the rest of puppet.  Does the fact seem to be affecting the manifest?







 On Sun, Jun 19, 2011 at 7:48 PM, josbal joshua.bald...@gmail.com wrote:
  Hi Guys,

  Was wondering if someone could point me in a way to diagnose my issue.

  I have a custom fact that i deployed on all my nodes. If i run the
  fact manually i get results as expected. When puppet runs only 5 or so
  nodes are storing this particular fact in the storeconfig mysql
  database. All other facts are storing fine for every node. As running
  the fact manually works on every node, i don't know why this fact for
  most nodes isn't populating in the database.

  Any ideas on how i could see what is happening within the puppet/
  facter processing?

  --
  You received this message because you are subscribed to the Google Groups
  Puppet Users group.
  To post to this group, send email to puppet-users@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.

-- 
You received this message because you are subscribed to the Google Groups 
Puppet Users group.
To post to this group, send email to puppet-users@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.

Re: [Puppet Users] Adding LDAP users to system group

2011-06-20 Thread romuald FREBAULT

hi,

i'm maybe misunderstanding your quetiosn but for me there's 2 ways doing
thaht:

first with exec

exec {add_user_to_group:
command = usermod -G mysql $user,
unless = getent group mysql | grep $user
}

this will add mysql as secondary group for $user

user {$user:
groups = [primarygroup,mysql]

}

this will do the same

but for me, the best would be to handle this by your ldap configuration with
something like this

http://blog.dimaj.net/2010/07/howto-verify-that-a-member-is-part-of-a-secondary-group-in-openldap/

2011/6/14 Gareth Allen gal...@openworld.co.za

Hi all,

All our users are stored in LDAP, but I need to add users to a system
group for sudo rules. Is there a way to do this without having Puppet
manage the user? For example:
getent passwd gareth.allen
gareth.allen:XX:1100:1100:Gareth Allen:/home/gareth.allen:/bin/bash

/etc/group contents:
mysql:x:27:

Now, I need Puppet to do the following:
mysql:x:27:gareth.allen

The only way I can think of doing this is by having Puppet manage
/etc/groups, but I'm a bit nervous of going that route. Does anyone
have any ideas?

Thanks,
Gareth

--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@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.

44 matches

Mail list logo