puppet kick as sudo fails

189 views
Skip to first unread message

Andy Adman

unread,
May 16, 2014, 6:26:51 AM5/16/14
to puppet...@googlegroups.com
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
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 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
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

Dirk Heinrichs

unread,
May 16, 2014, 8:54:02 AM5/16/14
to puppet...@googlegroups.com
Am 16.05.2014 12:26, schrieb Andy Adman:

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

Your $HOME is different than foreman's. Puppet looks into $HOME/.puppet for it's certs.

HTH...

    Dirk
--

Dirk Heinrichs, Senior Systems Engineer, Engineering Solutions
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Tel: +49 2226 1596666 (Ansage) 1149
Email: d...@recommind.com
Skype: dirk.heinrichs.recommind
www.recommind.com

Dirk Heinrichs

unread,
May 16, 2014, 8:56:31 AM5/16/14
to puppet...@googlegroups.com
Am 16.05.2014 12:26, schrieb Andy Adman:

Warning: Puppet kick is deprecated.

Maybe mcollective is what you want.

Bye...
Reply all
Reply to author
Forward
0 new messages