Designate HA may result in Resource not running res_designate_haproxy
Bug #1839021 reported by
David Ames
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Charm Helpers |
Triaged
|
Medium
|
Unassigned | ||
OpenStack Designate Charm |
Invalid
|
High
|
David Ames | ||
OpenStack HA Cluster Charm |
Confirmed
|
Undecided
|
Unassigned | ||
OpenStack Keystone Charm |
Invalid
|
Undecided
|
Unassigned | ||
charm-interface-hacluster |
Fix Released
|
High
|
Unassigned |
Bug Description
Designate HA may result in Resource not running res_designate_
Particularly running the full designate_ha openstack-mojo-spec with xenial <= queens.
Investigate timing, and compare for similarities with LP Bug##1837401.
Work around:
crm resource cleanup res_designate_
Changed in charm-interface-hacluster: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → David Ames (thedac) |
Changed in charm-designate: | |
status: | Triaged → Invalid |
Changed in charm-keystone: | |
status: | Confirmed → Invalid |
assignee: | Alex Kavanagh (ajkavanagh) → nobody |
Changed in charm-helpers: | |
status: | New → Triaged |
importance: | Undecided → Medium |
To post a comment you must log in.
Confirmed. I've seen this with keystone and swift as well. I'll dig into this further today.