TripleO affected templates: collectd-environment.yaml logging-environment.yaml We do not allow multiple servers to be specified in those environment files. We are looking for MonitoringRabbitHost server redundancy. Templates example: #### Sensu settings #### MonitoringRabbitHost: 10.10.10.10 MonitoringRabbitPort: 5672 MonitoringRabbitUserName: sensu MonitoringRabbitPassword: sensu MonitoringRabbitUseSSL: false MonitoringRabbitVhost: "/sensu"
Hey Robin, so affected template is /usr/share/openstack-tripleo-heat-templates/environments/monitoring-environment.yaml, correct? I'm asking because MonitoringRabbit* parameters are not part of collectd-environment.yaml or logging-environment.yaml. I'm gonna check if sensu puppet module supports multiple rabbitmq host already. If yes, the you should be able to provide multiple host already. If not, we will have to implement this feature. Please stay tuned.
Hi, yes sorry ffix it in the monitoring-environment.yaml.
So bad new is that the currently used parameter is not supporting multiple RabbitMQ hosts. The good new is that there is rabbitmq_cluster parameter implemented already in the puppet module, so the change will be required only on the level of tripleo-heat-templates.
Was able to deploy with MonitoringRabbitCluster configuration. Tested with 2 rabbit cluster nodes. Did sensu sanity with rabbit cluster. Looks ok. openstack-tripleo-heat-templates-8.0.0-0.20180227121938.e0f59ee.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:2086