volume only deployment creates non-functional api haproxy backend
Bug #1779310 reported by
Andrea Ieri
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Cinder Charm |
Fix Released
|
Medium
|
Alvaro Uria |
Bug Description
Deploying a volume only unit generates incorrect haproxy config.
To reproduce:
juju deploy cinder cinder-volume --config enabled-
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.
description: | updated |
tags: | added: canonical-bootstack |
Changed in charm-cinder: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in charm-cinder: | |
assignee: | nobody → Alvaro Uria (aluria) |
milestone: | none → 20.08 |
Changed in charm-cinder: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hi, One of customer's alerts is blocked by this bug, is there any update, please?