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

Error: Must pass rabbitmq_password to Class[Sensu] #31

Closed
twissmueller opened this issue Mar 1, 2013 · 2 comments
Closed

Error: Must pass rabbitmq_password to Class[Sensu] #31

twissmueller opened this issue Mar 1, 2013 · 2 comments

Comments

@twissmueller
Copy link
Contributor

I am trying to provision Sensu on vagrant box built with veewee (CentOS 6.3 minimal).

With librarian-puppet I get the modules apt, redis, rabbitmq and sensu.

The relevant part in the Vagrantfile looks like

...
config.vm.host_name = "sensu-sandbox"
config.vm.provision :puppet do |puppet|
    puppet.manifests_path = "puppet/manifests"
    puppet.manifest_file  = "main.pp"
end
...

And my main.pp looks like this:

node "sensu-sandbox" { 
  include sensu
  sensu { "localhost":
    rabbitmq_password => "sensupass",
    server => true
  }
}

The provisioning run ends with the following error message:

"Error: Must pass rabbitmq_password to Class[Sensu] at /tmp/vagrant-puppet/manifests/main.pp:3 on node sensu-sandbox"

I just don't get it ... While googling I found some pages suggesting to put the include statement at the end, but then I will end up with the following error message:

"Error: Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type sensu at /tmp/vagrant-puppet/manifests/main.pp:6 on node sensu-sandbox"

I get the same error when leaving out the include statement like in the README.

Any ideas what the problem could be?

@jlambert121
Copy link
Contributor

I think what you're looking for is:

class { 'sensu':
    rabbitmq_password => "sensupass",
    server => true
  }

(no 'include sensu' either)

@twissmueller
Copy link
Contributor Author

So much to learn there still is ...

Umpf, yes, that solved my problem.

Thanks a lot for your help!

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

2 participants