[Puppet Users] puppet kick as sudo fails

Andy Adman
Fri, 16 May 2014 10:26:51 -0000

Hey all,

i am a little confused, so i need some ideas. I have a
Foreman(PuppetMaster) server installed on Amazon EC2 and i am able to
provision instances to the same ec2 subnet.
After the provisioning i can run puppet from the agent and everything is
going well.
Ok, but i want to kick the puppet run from my PuppetMaster
(Foreman-Server). so i executed

$ /usr/bin/puppet kick --host 'webs.local.cloud'











* Warning: Puppet kick is deprecated. See
http://links.puppetlabs.com/puppet-kick-deprecation
<http://links.puppetlabs.com/puppet-kick-deprecation> Warning: Failed to
load ruby LDAP library. LDAP functionality will not be available Triggering
webs.local.cloud Notice: Using less secure serialization of reports and
query parameters for compatibility Notice: with older puppet master. To
remove this notice, please upgrade your master(s) Notice: to Puppet 3.3 or
newer. Notice: See http://links.puppetlabs.com/deprecate_yaml_on_network
<http://links.puppetlabs.com/deprecate_yaml_on_network> for more
information. Getting status status is success webs.local.cloud finished
with exit code 0 Finished*


  Ok nice. A strange notice cause my puppet version is 3.5.1 but ok its
running.
Now i want to execute the same command as sudo cause Foreman is doing the
same.

$ sudo /usr/bin/puppet kick --host 'webs.local.cloud'






*Warning: Puppet kick is deprecated. See
http://links.puppetlabs.com/puppet-kick-deprecation
<http://links.puppetlabs.com/puppet-kick-deprecation> Warning: Failed to
load ruby LDAP library. LDAP functionality will not be available Triggering
webs.local.cloud Error: Host webs.local.cloud failed: Server hostname
'webs.local.cloud' did not match server certificate; expected
d2eca8ab-ea7f-4ed0-a8d7-d9ee7d864816 webs.test.cloud finished with exit
code 2 Failed: webs.local.cloud*

Shit now it fails. I checked my sudoers rules and ok there is written:




*#includedir /etc/sudoers.d Defaults:foreman-proxy !requiretty
foreman-proxy ALL = NOPASSWD: /usr/bin/puppet kick * foreman-proxy ALL =
NOPASSWD: /usr/bin/puppet cert **

I also checked that the user foreman-proxy exists, but now I have no clue
what to do.

So maybe someone has an idea for me.

Thanks in advanced and greetings Andy

--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/2dc0af99-b1b2-44e7-9f5c-9f7ca5afcf74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.