Issue #7201 has been updated by Virgil M.

Status changed from Duplicate to Re-opened

The exact same thing happens with

<pre>
  puppet agent --version
  3.2.4
</pre>

Doing repeated puppet kicks to the same VM. We are waiting for the status file 
to be generated under

/var/lib/puppet/reports/[hostname]/status.txt
before re-issuing the kick.

This is on ubuntu 12.04

Looking for the ‘/var/lib/puppet/state/agent_catalog_run.lock’ file (on the 
agent machine) and waiting for it to go away makes thing work. This lock file 
remains set way after the puppet agent has sent the status back to the master 
(like 5-10 seconds )

Still hitting this; very annoying. Any ideas?


----------------------------------------
Bug #7201: [puppet2.7]puppet kick exit code 3
https://projects.puppetlabs.com/issues/7201#change-97466

* Author: joy huang
* Status: Re-opened
* Priority: High
* Assignee: 
* Category: server
* Target version: 
* Affected Puppet version: 
* Keywords: 
* Branch: 
----------------------------------------
1.when i run the following " puppet kick"command on puppet master,it return 
failed message:

<pre>
    [root@master puppet]# puppet kick -p 10 --host client.joy.com
    Triggering client.joy.com
    Getting status
    status is running
    Host client.joy.com is already running
    client.joy.com finished with exit code 3
    Failed: client.joy.com
</pre>

2.puppet agent relative setting is:
<pre>
    [root@client puppet]cat /etc/puppet/auth.conf
    path ~ ^/catalog/([^/]+)$
    method find
    allow $1
    path /certificate_revocation_list/ca
    method find
    allow *
    # allow all nodes to store their reports
    path /report
    method save
    allow *
    # inconditionnally allow access to all files services
    # which means in practice that fileserver.conf will
    # still be used
    path /file
    allow *
    ### Unauthenticated ACL, for clients for which the current master doesn't
    ### have a valid certificate
    # allow access to the master CA
    path /certificate/ca
    auth no
    method find
    allow *
    path /certificate/
    auth no
    method find
    allow *
    path /certificate_request
    auth no
    method find, save
    allow *
    path /run
    method save
    allow *
    # this one is not stricly necessary, but it has the merit
    # to show the default policy which is deny everything else
    path /
    auth any
    [root@client puppet]# cat namespaceauth.conf
    [fileserver]
    allow *
    [puppetmaster]
    allow *
    [puppetrunner]
    allow *
    [puppetbucket]
    allow *
    [puppetreports]
    allow *
    [resource]
    allow *
    [root@client puppet]# cat puppet.conf
    [main]
    confdir = /etc/puppet
    vardir=/var/lib/puppet
    logdir = $vardir/log
    # Where Puppet PID files are kept.
    # The default value is $vardir/run.
    rundir = $vardir/run
    # The default value is $confdir/ssl.
    ssldir = $confdir/ssl
    [agent]
    pidfile = /var/lib/puppet/run/agent.pid
    classfile = $vardir/state/classes.txt
    localconfig = $vardir/localconfig
    server = master.joy.com
    #report = true
    listen = true
</pre>

3.[root@client puppet]# netstat -lntp
<pre>
    Proto Recv-Q Send-Q Local Address               Foreign Address             
State       PID/Program name
    tcp        0      0 0.0.0.0:8139                0.0.0.0:*                   
LISTEN      2515/ruby
</pre>    

The "puppetrun problem" is bothering me for a long time ,from puppet2.6.XX to 
puppet 2.7 release.

I need your help!
 
any suggestion is welcome
    Thanks
    joy



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to