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

stderr of the which command shows during Puppet runs on agent nodes #241

Closed
natemccurdy opened this issue Aug 11, 2015 · 2 comments
Closed
Labels
bug Something isn't working

Comments

@natemccurdy
Copy link

After the commit that added in a custom fact for r10k_path (1780577), my agent nodes (non-masters) are showing the text below during Puppet runs.

Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts 
/usr/bin/which: no r10k in (/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/root/bin)
...

What's happening is that which can't find r10k on my agents because r10k isn't installed on them. The stderr of which gets sent to the output of the Puppet run and totally ruins my day.

The r10k_path custom fact should catch stderr and hide it. Even better would be to not shell out to which and instead use native ruby to do this.

Maybe do something like http://stackoverflow.com/a/6624392

@natemccurdy natemccurdy added the bug Something isn't working label Aug 11, 2015
@acidprime
Copy link
Collaborator

fixed in f9e253d

@acidprime
Copy link
Collaborator

Released in v3.1.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants