Issue #1893 has been updated by luke.

Status changed from Re-opened to Closed

This is probably a Facter bug - there was one filed where Facter is clobbering 
the PATH.  The bug was fixed in 1.5.3, I think, so if you're running 1.5.2 you 
might be being hit by it.  Try up- or down-grading.
----------------------------------------
Feature #1893: Package resource unable to find gem binary in alternate path
http://projects.reductivelabs.com/issues/1893

Author: mbrannigan
Status: Closed
Priority: Normal
Assigned to: 
Category: 
Target version: 
Complexity: Unknown
Affected version: 0.24.7
Keywords: 


In our environment, ruby is installed under /opt/local/bin.  When I use the gem 
provider, I get the following error message:

<pre>
Jan 26 11:17:37 HOST puppetd[25024]: [ID 702911 daemon.error] Could not
prefetch package provider 'gem': Could not list gems: Execution of 'no gem
in /bin /sbin /usr/bin /usr/sbin /usr/local/sbin /usr/local/bin list --local'
returned 1: 
</pre>

Everything is fine if I create a symlinks for /opt/local/bin/ruby and 
/opt/local/bin/gem in /usr/local/bin.  /opt/local/bin is in the system PATH.

Would it be possible to have a configuration option to provide a search path 
for puppetd or perhaps a path attribute on the Package resource?
I tried a few things as a work-around and I can't seem to munge the search path 
for the puppetd process.

Thanks!
--- Mike Brannigan


----------------------------------------
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://reductivelabs.com/redmine/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