Deploying availability monitoring without SSL as documented does not work

[David Noriega]

As documented, attempting to deploy the availability monitoring feature does not work as the sensu client is unable to connect to the monitoring host's rabbitmq service. The generated /etc/sensu/conf.d/rabbitmq.json config file has ssl enabled, regardless of it being disabled via the TripleO framework.

Removing the ssl directive from sensu's configuration fixes the agent and I've filed a bug with the puppet-sensu project who confirmed the issue https://github.com/sensu/sensu-puppet/issues/1050 and have a pending patch. I will also be submitting a patch to the tripleo-heat-templates with a workaround that prevents the puppet-sensu package from generating a config with ssl enabled when it should not.

Environment:
CentOS - 7.4
OpenStack - Pike

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/633281

[Juan Antonio Osorio Robles (juan-osorio-robles)]

Is this still being worked on?

[OpenStack Infra (hudson-openstack)]

Change abandoned by wes hayutin (<email address hidden>) on branch: master
Review: https://review.opendev.org/633281
Reason: https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html