-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid parameter ruby at manifests/gem.pp #41
Comments
Can you provide more information about your issue? Can you paste the code you are using? (OS, platform etc.) |
@LegionSB Is this still an issue? |
Sorry for the slow follow-up. As of now, I am no longer experiencing this issue. HEAD is working with ostensibly the same manifests I was experiencing the issue with before. I will close. |
Well it seems I have the same problem: puppet: 2.7.19-1puppetlabs2
err: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter ruby at /etc/puppet/modules/rbenv/manifests/gem.pp:28 This is for version cloned straight from git repo and also when I do "puppet module install/upgrade alup-rbenv" For version "alup-rbenv (v1.0.0)" things seems to be fairly ok, any ideas? |
I met the same problem as you did. err: Could not retrieve catalog from remote server: Error 400 on SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type rbenvgem at /etc/puppet/staging/modules/rbenv/manifests/gem.pp:28 on node sydgsstagserv4.frontfoot.net.au In my site.pp rbenv::gem { "puma": My OS version CentOS5.8 x86_64 As I think, puppet agent is unable to load $modules_path/rbenv/lib, inside which there is a default.rb to define rbenvgem. But I have no idea how to load $modules_path/rbenv/lib during puppet compilation. |
Since updating to the latest version of puppet-rbenv, my runs all error with:
Invalid parameter ruby at /etc/puppet/modules/rbenv/manifests/gem.pp:28
My current workaround is to revert to the Sept 20 commit c33eca8, and my runs begin functioning again.
The text was updated successfully, but these errors were encountered: