You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 ofwhich
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 towhich
and instead use native ruby to do this.Maybe do something like http://stackoverflow.com/a/6624392
The text was updated successfully, but these errors were encountered: