Closed daenney closed 12 years ago
Off the top of my head:
1) Did you include rvm
somewhere in your manifest file?
2) Did you add
[main]
pluginsync = true
to your /etc/puppet/puppet.conf
file. Sometimes this can cause the module to not be downloaded to the client.
Yes, rvm itself is getting installed so that part is fine and yes, pluginsync is enabled.
I'm rather confused as well 'cause I can't really find a valid reason for the error. The only thing I could think of was a typo, which doesn't seem to be the case or something along hte lines of this issue: http://projects.puppetlabs.com/issues/5368.
I just can't nail down where exactly it's going wrong no matter how much debug output Puppet gives me...
What version of puppet are you using? I know I say puppet-rvm is compatible with 2.6.7 and later, but honestly I haven't been testing that lately and it's possible it may no longer work on older versions. Would it be possible to try 2.7.10 or newer? apt.puppetlabs.com may help if you're on Ubuntu/Debian.
We're on the latest version of puppet:
ii facter 1.6.9-1puppetlabs1 Ruby module for collecting simple facts about a host operating system
ii puppet 2.7.14-2puppetlabs1 Centralized configuration management - agent startup and compatibility scripts
ii puppet-common 2.7.14-2puppetlabs1 Centralized configuration management
The only thing I can think of is that this breaks because I removed the stages, but it really shouldn't (stages was causing a dependency cycle).
Found it, it's a puppet bug in my case: http://projects.puppetlabs.com/issues/13858
I'm running into an error I can't figure out...
What I've done is add this to
manifests/init.pp
:I figured one should be able to do this and since I want at least that ruby to be available on every machine that gets RVM I figured this should be as good as any place to do it.