Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Agent activation fails on mcollective 2.8.6 (open source puppet 4.2) #254

Closed
gusmat opened this issue Nov 6, 2015 · 1 comment
Closed

Comments

@gusmat
Copy link

gusmat commented Nov 6, 2015

Hi, thanks for this module.
I'm trying to get the r10k mco agent working on mcollective 2.8.6.
The module installs the agent in the wrong path (#245) and after fixing that and restarting MCollective it throws this error in mcollective.log:

D, [2015-11-06T20:35:56.043076 #3993] DEBUG -- : agents.rb:104:in `block in findagentfile' Found r10k at /opt/puppetlabs/mcollective/plugins/mcollective/agent/r10k.rb
D, [2015-11-06T20:35:56.043141 #3993] DEBUG -- : pluginmanager.rb:167:in `loadclass' Loading MCollective::Agent::R10k from mcollective/agent/r10k.rb
D, [2015-11-06T20:35:56.046595 #3993] DEBUG -- : agents.rb:67:in `loadagent' Not activating agent r10k due to agent policy in activate? method

This is on a Amazon Linux running ruby 2.1.7, puppet 4.2 and mcollective 2.8.6

Thanks

@gusmat
Copy link
Author

gusmat commented Nov 7, 2015

Please ignore this issue. The problem was on the way that the binaries path was being set (via profile.d), which caused the agent to fail to find r10k.

@gusmat gusmat closed this as completed Nov 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant