| 2018-06-29 12:31:05 |
Andrea Ieri |
description |
Deploying a volume only unit generates incorrect haproxy config.
To reproduce:
juju deploy cinder cinder-volume --config enabled-services=volume
juju add-relation cinder-volume
juju add-relation cinder-volume rabbitmq-server
The above yields the following haproxy.cfg stanza:
backend cinder_api_<ip>
balance leastconn
server cinder-volume-1 <ip>:8766 check
The backend is however not functional as cinder-api is not started and nothing is listening on port 8766
This would be rather harmless, except that when our nagios haproxy check validates backends, it will alert for that bogus entry. |
Deploying a volume only unit generates incorrect haproxy config.
To reproduce:
juju deploy cinder cinder-volume --config enabled-services=volume
juju add-relation cinder-volume mysql
juju add-relation cinder-volume rabbitmq-server
The above yields the following haproxy.cfg stanza:
backend cinder_api_<ip>
balance leastconn
server cinder-volume-1 <ip>:8766 check
The backend is however not functional as cinder-api is not started and nothing is listening on port 8766
This would be rather harmless, except that when our nagios haproxy check validates backends, it will alert for that bogus entry. |
|
