Issue #15717 has been updated by Josh Cooper.

Status changed from In Topic Branch Pending Review to Merged - Pending Release
Affected Puppet version set to 3.0.0

This is merged into 3.0.x in 
<https://github.com/puppetlabs/puppet/commit/3aaa582>

During the removal of the XMLRPC code, a line requiring 'puppet/run' was 
accidentally removed, causing this issue. This commit restores puppet kick 
functionality on the remote agent side. It also adds an acceptance test to 
ensure that the remote agent responds to puppet kick requests.

Note that `puppet kick --ignoreschedules` is still broken and has been since at 
least 2.6.4, see #5975.

Although `puppet kick` accepts a --(no-)pluginsync command line argument, it is 
not meaningful, as the remote agent always determines whether or not to perform 
a pluginsync based on how it is configured. And in Puppet 3, pluginsync is 
enabled by default.
----------------------------------------
Bug #15717: puppet kick returns "Error: Could not find indirection 'run' / 
testip.example.com finished with exit code 2"
https://projects.puppetlabs.com/issues/15717#change-72602

Author: Sandra Schlichting
Status: Merged - Pending Release
Priority: Normal
Assignee: Josh Cooper
Category: 
Target version: 3.0.1
Affected Puppet version: 3.0.0
Keywords: puppet kick
Branch: https://github.com/puppetlabs/puppet/pull/1200


Would like to be able to use "puppet kick testip.example.com".

Using CentOS6.3 on both puppetmaster and node with puppet 3rc3 from 
yum.puppetlabs.com.

IPtables is not running on any of them.

Bottom of node /etc/puppet/auth.conf

    path /run
    auth yes
    allow puppet.imm.dtu.dk
    
    path /
    auth any

Node /etc/puppet/puppet.conf

Appended:

    listen = true
    report = true

I can do "puppet agent --test" on the node, and it pulls the changes fine.

If I on the puppetmaster do

    [root@puppet ~]# puppet kick  testip.example.com --debug --trace 
--foreground
    Triggering testip.example.com
    testip.example.com finished with exit code 2
    Failed: testip.example.com

and on the node I see

    [root@testip ~]# puppet agent --listen --debug --no-daemonize --verbose
    Info: access[^/catalog/([^/]+)$]: allowing 'method' find
    Info: access[^/catalog/([^/]+)$]: allowing $1 access
    Info: access[^/node/([^/]+)$]: allowing 'method' find
    Info: access[^/node/([^/]+)$]: allowing $1 access
    Info: access[/certificate_revocation_list/ca]: allowing 'method' find
    Info: access[/certificate_revocation_list/ca]: allowing * access
    Info: access[/report]: allowing 'method' save
    Info: access[/report]: allowing * access
    Info: access[/file]: allowing * access
    Info: access[/certificate/ca]: adding authentication any
    Info: access[/certificate/ca]: allowing 'method' find
    Info: access[/certificate/ca]: allowing * access
    Info: access[/certificate/]: adding authentication any
    Info: access[/certificate/]: allowing 'method' find
    Info: access[/certificate/]: allowing * access
    Info: access[/certificate_request]: adding authentication any
    Info: access[/certificate_request]: allowing 'method' find
    Info: access[/certificate_request]: allowing 'method' save
    Info: access[/certificate_request]: allowing * access
    Info: access[/run]: adding authentication any
    Info: access[/run]: allowing 'method' save
    Info: access[/run]: allowing puppet.imm.dtu.dk access
    Info: access[/]: adding authentication any
    Info: Inserting default '/status' (auth true) ACL because none were found 
in '/etc/puppet/auth.conf'
    Error: Could not find indirection 'run'



-- 
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 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-bugs?hl=en.

Reply via email to