Skip to content
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

Closed
brendonrapp opened this issue Oct 18, 2012 · 5 comments
Closed

Invalid parameter ruby at manifests/gem.pp #41

brendonrapp opened this issue Oct 18, 2012 · 5 comments

Comments

@brendonrapp
Copy link

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.

@alup
Copy link
Owner

alup commented Oct 21, 2012

Can you provide more information about your issue? Can you paste the code you are using? (OS, platform etc.)

@alup
Copy link
Owner

alup commented Nov 3, 2012

@LegionSB Is this still an issue?

@brendonrapp
Copy link
Author

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.

@fluential
Copy link

Well it seems I have the same problem:

puppet: 2.7.19-1puppetlabs2
Ubuntu 10.10 x86_64

 rbenv::install { "root":
      group => 'root',
      home  => '/tmp/rubytest'
  }

  rbenv::compile { "1.9.3-p194":
     user => "root",
     home => "/tmp/rubytest",
  }

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?

@sebastienliu
Copy link

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
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run

In my site.pp

rbenv::gem { "puma":
user => 'www',
ruby => '1.9.3-p327',
gem => 'bundler',
}

My OS version CentOS5.8 x86_64
Puppet version : 2.7.6

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants