encountering general issues related to running puppet as root

[jonoterc]

Hi, I'm seeing regular issues related to running puppet as root- these are generally ownership issues where rvm commands affected puppet-rvm-nstalled elements fail when run under a non-privileged user account (due insufficient permissions).

Just to pick the latest issue I'm seeing, a puppet-rvm-installed ruby's rubygems can't be easily updated or turned off via "rvm rubygems VERSION" - an ugly workaround of "rvmsudo rvm ruby gems VERSION" works instead, but only by granting the user sudoer privileges.

I can reference other issues, but before I take up anyone's time, this seems like a potentially icky enough problem that I rather assume I'm somehow approaching this the wrong way? For example, is this module only intended for being run under a non-privileged puppet run, or is there a way to configure puppet so that just the puppet-rvm's actions are run non-privileged?

Thanks!

[carlossg]

we install rvm and rubies running puppet as root and then there's another user that does all the rvm stuff

do you have the user in the 'rvm' group?

[jonoterc]

Thanks for the reply! I'm using "rvm_system_user" to add the (also puppet-created) to the 'rvm' group, which has been working as expected. The problems manifest when using rvm_gemset and rvm_gem to set-up gem sets and individual gems (putting together a default development environment), once non-root users start trying to modify the gemset/gem environment) - if I understand you correctly then I should only run puppet with those commands as another (non-root) rvm user?

[carlossg]

I don't use rvm_gem or rvm_gemset. Could you create a test in https://github.com/maestrodev/puppet-rvm/blob/maestrodev/spec/system/rvm_system_spec.rb to illustrate the issue you are having?
Everything should work when puppet runs as root