Invalid parameter ssl_transport on Sensu_rabbitmq_config

[poolski]

Since the ssl_transport parameter got added in 1.2.0, my Sensu puppet module has ceased to work. I get this error, despite having all the configs correct, insofar as I can tell.

Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter ssl_transport on Sensu_rabbitmq_config[server.company.com] at /etc/puppet/environments/develop/modules/sensu/manifests/rabbitmq/config.pp:80 on node server.company.com

Am I missing something bleedingly obvious?

[jlambert121]

Do you have just rabbitmq_ssl => true without rabbitmq_ssl_private_key or rabbitmq_ssl_cert_chain defined?

I ran into some stuff upgrading my environment late last week that while ssl: true in the rabbitmq.json (for sensu to be happy if your cert is trusted by the system), it appears the puppet module now wants that to be an object. I needed to add rabbitmq_ssl_cert_chain => "/etc/ssl/certs/ca-bundle.crt" to my config so puppet would be happy. I haven't looked into the sensu config yet to see what "the right way" to configure it is yet though.

[poolski]

No, I have all three defined in hiera:

"sensu::rabbitmq_ssl": true,
"sensu::rabbitmq_ssl_cert_chain": "puppet:///modules/sensu_site/ssl/cert.pem",
"sensu::rabbitmq_ssl_private_key": "puppet:///modules/sensu_site/ssl/key.pem",

On 20 October 2014 14:56, Justin Lambert notifications@github.com wrote:

Do you have just rabbitmq_ssl => true without rabbitmq_ssl_private_key or
rabbitmq_ssl_cert_chain defined?

—
Reply to this email directly or view it on GitHub
#263 (comment).

kyrill

[jaxxstorm]

I have the same problem, and I'm in the same boat as @poolski - have all the options defined in hiera but get invalid parameter.

[jaxxstorm]

Ah, well that was easy. You need to restart your Puppetmaster! See this bug for details:

http://projects.puppetlabs.com/issues/17814
https://tickets.puppetlabs.com/browse/PUP-1515

I would recommend any newly tagged module releases have a note that says there are changes to custom provider types and subsequently need a PuppetMaster restart. I can't think of anything that would trigger this on the PM, so will need a manual restart. Bit of a pain in the arse.

To be more specific, this only seems to be an issue if you're using Puppet's environments. If you're testing this new module in a new branch, because of the new provider types added, you'll need to restart your PM once you've committed to a new branch.

@poolski can you confirm this fixes it for you too?

[ghost]

I can confirm that restarting my puppet master didn't fix the problem for me.

[jlambert121]

@Craft--- you're getting the same error? What are the rabbitmq_ssl* settings you're using? There was a merge today that that ensured the rabbitmq_ssl parameter got set correctly - does that fix things for you?

[jlambert121]

@Craft--- I'm going to close this, please open a new ticket if you're still having issues.