When pausing hacluster and principal unit, haproxy still references stopped unit in backends

Bug #1929609 reported by Drew Freiberger
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack API Layer
New
Undecided
Unassigned

Bug Description

I believe the openstack api layer is the correct place for this bug.

We are seeing issues with paused units still being referenced by haproxy from other HA peer units.

As an example, deploy 3 units of designate on focal-ussuri with https endpoints (via vault:certificates relation)
Then 'run-action pause' against one of the designate units and it's hacluster-designate unit.

Then every 3rd or so hit to 'openstack zone list --all' returns:
Failed to contact the endpoint at https://designate.mysite.com:9001 for discovery. Fallback to using that endpoint as the base url.
NotFound

This seems to be related to there being no healthcheck routine within the haproxy backend configuration templates.

summary: - When pausing hacluster and designate unit, haproxy still references
+ When pausing hacluster and principal unit, haproxy still references
stopped unit in backends
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.