Issue #22762 has been reported by Kristian Glass.
----------------------------------------
Bug #22762: Puppet uses inherited unclean environment when starting services
https://projects.puppetlabs.com/issues/22762
* Author: Kristian Glass
* Status: Unreviewed
* Priority: Normal
* Assignee:
* Category:
* Target version:
* Affected Puppet version:
* Keywords:
* Branch:
----------------------------------------
I'm running masterless Puppet from inside a bundle: `bundle exec puppet apply
$etc`
I'm using Sensu, with the `sensu/sensu` module from the forge.
My puppet runs consistently fail to start Sensu; modifying the Sensu init
scripts to dump the environment shows that it's full of environment variables
from the `bundle exec`, including, crucially:
BUNDLE_BIN_PATH=/usr/lib/ruby/bin/bundle
BUNDLE_GEMFILE=/opt/footballradar/puppet/Gemfile
RUBYOPT=-I/usr/lib/ruby/vendor_ruby -rbundler/setup
and more. Sensu, unsurprisingly, doesn't like being started with environment
config from a wholly different bundle.
It seems a bug that Puppet doesn't do any kind of environment sanitisation such
that the Puppet environment doesn't leak into that of services.
--
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 unsubscribe from this group and stop receiving emails from it, send an email
to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
