Module assumes there's a rvm group

[ghost]

Error: Could not set 'file' on ensure: Could not find group rvm at 8:/etc/puppet/modules/rvm/manifests/rvmrc.pp
Error: Could not set 'file' on ensure: Could not find group rvm at 8:/etc/puppet/modules/rvm/manifests/rvmrc.pp
Wrapped exception:
Could not find group rvm
Error: /Stage[main]/Rvm::Rvmrc/File[/etc/rvmrc]/ensure: change from absent to file failed: Could not set 'file' on ensure: Could not find group rvm at 8:/etc/puppet/modules/rvm/manifests/rvmrc.pp

[TJM]

I second this, shouldn't the rvm-install create that group?

[TJM]

OK, I think I have figured it out..

Here is the error:

Info: Class[Rvm::Rvmrc]: Starting to evaluate the resource
Info: Class[Rvm::Rvmrc]: Evaluated in 0.00 seconds
Info: /Stage[main]/Rvm::Rvmrc/File[/etc/rvmrc]: Starting to evaluate the resource
Error: Could not set 'file' on ensure: Could not find group rvm at 14:/vagrant/puppet/modules/rvm/manifests/rvmrc.pp
Error: Could not set 'file' on ensure: Could not find group rvm at 14:/vagrant/puppet/modules/rvm/manifests/rvmrc.pp
Wrapped exception:
Could not find group rvm
Error: /Stage[main]/Rvm::Rvmrc/File[/etc/rvmrc]/ensure: change from absent to file failed: Could not set 'file' on ensure: Could not find group rvm at 14:/vagrant/puppet/modules/rvm/manifests/rvmrc.pp
Info: /Stage[main]/Rvm::Rvmrc/File[/etc/rvmrc]: Evaluated in 0.01 seconds

The reason is relating to https://github.com/maestrodev/puppet-rvm/blob/maestrodev/manifests/init.pp#L24 ... It calls rvm_system_users with an empty array (if you just use include rvm). This doesn't actually create any resources, and thus https://github.com/maestrodev/puppet-rvm/blob/maestrodev/manifests/system_user.pp#L8 doesn't get a chance to create the "rvm" group. Since that rvmrc is before => Exec['system-rvm'], the "rvm-install" doesn't get a chance to run and create the rvm group like it used to.

I wonder if moving the ensure_resource('group', $group, {'ensure' => 'present' }) to init.pp would fix it?

[TJM]

My pull request is above to fix this, but I also found a workaround...

Basically add a "rvm::system_users" parameter to your hiera data or call the class like this:

class { 'rvm':
  system_users => ['root'],
}

... this is only necessary till my pull request #21 is merged. Then you can go back to using include rvm

~tommy

[carlossg]

fixed in 1.4.1, thanks