HAproxy is restarted every 5-10 minutes when using reactive charms with multiple network space bindings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Gnocchi Charm |
Fix Released
|
High
|
James Page | ||
OpenStack Designate Charm |
Fix Released
|
High
|
Liam Young | ||
charms.openstack |
Fix Released
|
High
|
James Page |
Bug Description
There is designate application running in the clustered mode based on 17.11 charm release. The following is being observed:
root@juju-
2017-12-12 13:50:24 DEBUG ha-relation-changed * Stopping haproxy haproxy
2017-12-12 13:55:49 DEBUG ha-relation-changed * Stopping haproxy haproxy
2017-12-12 14:07:24 DEBUG ha-relation-changed * Stopping haproxy haproxy
2017-12-12 14:12:30 DEBUG ha-relation-changed * Stopping haproxy haproxy
2017-12-12 14:22:56 DEBUG ha-relation-changed * Stopping haproxy haproxy
2017-12-12 14:27:46 DEBUG ha-relation-changed * Stopping haproxy haproxy
2017-12-12 14:37:22 DEBUG ha-relation-changed * Stopping haproxy haproxy
2017-12-12 14:43:07 DEBUG ha-relation-changed * Stopping haproxy haproxy
2017-12-12 14:54:02 DEBUG ha-relation-changed * Stopping haproxy haproxy
2017-12-12 15:00:02 DEBUG ha-relation-changed * Stopping haproxy haproxy
HAproxy is being restarted every 5-10 minutes. Attaching log files from all 3 units.
summary: |
HAproxy is restarted every 5-10 minutes when using clustered designate - application from 17.11 charm release + application |
summary: |
- HAproxy is restarted every 5-10 minutes when using clustered designate - application + HAproxy is restarted every 5-10 minutes when using designate application |
Changed in charm-designate: | |
status: | Fix Committed → Fix Released |
Changed in charm-gnocchi: | |
status: | Fix Committed → Fix Released |
This issue was originally reported in bug 1698814 and is claimed to be fixed in designate charm 17.08 release.