glance charm leaves old entries in haproxy.cfg when adding and removing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Glance Charm |
Fix Released
|
Medium
|
Alex Kavanagh | ||
glance (Juju Charms Collection) |
Invalid
|
Medium
|
Alex Kavanagh |
Bug Description
I have a requirement to temporarily add an extra unit to a Openstack HA setup, Liberty on Trusty using charms 15.10.
Aside from the fact that there is manual work required to do this, as per LP#1400481, I'm running into an issue when doing the juju add-unit and then juju remove-unit that the haproxy.cfg ends up keeping the removed unit in the backend glance_api section.
This does not occur when I do the same process for cinder.
--- Test Case ---
On juju management server:
$ juju add-unit glance --to lxc:#
... wait a while ..
On unit to be removed:
$ sudo service pacemaker stop ; sudo service corosync stop
On another unit of the service we're working on:
$ sudo crm_node -R <node>
Back on the juju management server:
$ juju remove-unit glance/#
When checking /etc/haproxy/
Versions:
$ juju --version
1.25.5-trusty-amd64
$ dpkg-query -W maas
maas 1.9.2+bzr4568-
Glance charm is lp:charms/trusty/glance revno 127.
Please let me know if you need any further information.
Changed in glance (Juju Charms Collection): | |
importance: | Undecided → Medium |
milestone: | none → 16.10 |
Changed in charm-glance: | |
assignee: | nobody → Alex Kavanagh (ajkavanagh) |
importance: | Undecided → Medium |
status: | New → Fix Committed |
Changed in glance (Juju Charms Collection): | |
status: | Fix Committed → Invalid |
Changed in charm-glance: | |
milestone: | none → 17.02 |
Changed in charm-glance: | |
status: | Fix Committed → Fix Released |
I've verified this with a minimal bundle, and after a glance unit is removed, it is still present in haproxy.cfg.