Issue #15717 has been updated by eric sorenson. Assignee changed from eric sorenson to Andrew Parker
Daniel pointed the way here -- nothing was requiring the model for the indirector with a `require 'puppet/run'` ; the fact that the xmlrpc handler was the only place in the agent application load path that did so had been latent in the 4000 deleted lines. Once I added it to application/agent.rb, I got a new error: <pre> Error: Could not intern from pson: Run does not accept pluginsync /Users/eric/Sandbox/puppet/lib/puppet/run.rb:29:in `block in initialize' /Users/eric/Sandbox/puppet/lib/puppet/run.rb:28:in `each' /Users/eric/Sandbox/puppet/lib/puppet/run.rb:28:in `initialize' /Users/eric/Sandbox/puppet/lib/puppet/run.rb:71:in `new' /Users/eric/Sandbox/puppet/lib/puppet/run.rb:71:in `from_pson' /Users/eric/Sandbox/puppet/lib/puppet/network/formats.rb:130:in `data_to_instance' /Users/eric/Sandbox/puppet/lib/puppet/network/formats.rb:107:in `intern' /Users/eric/Sandbox/puppet/lib/puppet/network/format_handler.rb:12:in `protect' </pre> This is because the options hash in `self.from_pson` on `lib/puppet/run.rb:66` is initialized with a key name pluginsync, whose value is the pluginsync setting; but the `initialize` method only accepts `:tags` and `:ignoreschedules` as valid options, not `:pluginsync`. The originating change is from a fix for #15668, here: https://github.com/puppetlabs/puppet/commit/62420c6ff02133e7bf6254cff83ddb3511a1ea41#L6L66 -- I believe this should be reverted but don't understand the scope of #15668 well enough to be confident about it. Passing to Andy who did the #15668 work. ---------------------------------------- Bug #15717: Error: Could not find indirection 'run' / testip.example.com finished with exit code 2 https://projects.puppetlabs.com/issues/15717#change-72213 Author: Sandra Schlichting Status: Accepted Priority: Normal Assignee: Andrew Parker Category: Target version: 3.0.x Affected Puppet version: Keywords: puppet kick Branch: 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.
