In Puppet 3 Puppet does its absolute best to make sure $HOME, $USER and
$LOGNAME environment variables are unset and nowhere to be found. I realise
this change was necessary because it caused some weird start-up issues with
Puppet but this also killed our RabbitMQ module.
RabbitMQ is written in Erlang and that thing _requires_ a $HOME to be set
as it will try to write an erlang-cookie to it and horribly fail and go up
in flames if it can't. Since Puppet 3 every Exec we have in the RabbitMQ
module now fails because of this. We've tried changing the command to
'$HOME=/var/lib/misc/puppet rabbitmqctl <do something>' but yet again the
Exec type just nukes the environment too. This being the 'offending' pull
request which got
So, short of patching Puppet to not do this or generate static wrappers for
every rabbitmqctl command which then in turn get called by an Exec, how do
we solve this? I really don't feel like generating wrappers for every Exec
that needs one of those environment variables set. I'd actually expect that
Exec would allow me to explicitly pass in environment variables that I
really need set in that case but the docs don't seem to know anything about
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/iOy3L_m66GUJ.
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to email@example.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.