keepalived track script fails sometimes
Bug #2025219 reported by
Michal Nasiadka
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
kolla-ansible | Status tracked in Bobcat | |||||
Antelope |
Fix Committed
|
Medium
|
Michal Nasiadka | |||
Bobcat |
Fix Committed
|
Medium
|
Michal Nasiadka | |||
Yoga |
New
|
Medium
|
Unassigned | |||
Zed |
Fix Committed
|
Medium
|
Michal Nasiadka |
Bug Description
Observed mainly in CI on single node deployments
In some occasions (sometimes rare, sometimes more often - most often it surfaces in upgrade jobs) the standard keepalived track script that checks haproxy state via a socket - times out.
In those occurrences - keepalived fails and goes into BACKUP state for some seconds - which breaks API connectivity.
In case of multinode - there's always another node to fail over to - but in single node - not really.
Changed in kolla-ansible: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/c/openstack /kolla- ansible/ +/887069 /opendev. org/openstack/ kolla-ansible/ commit/ 8d5356268688645 efbd09517059cbc 1189e3fea7
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/2023.1
commit 8d5356268688645 efbd09517059cbc 1189e3fea7
Author: Michal Nasiadka <email address hidden>
Date: Tue Jun 27 09:42:31 2023 +0200
loadbalancer: Add option to not define track script
We've seen issues in CI when keepalived haproxy check script returns
an error and keepalived is switching to backup and then again to primary
on a single node environment.
Closes-Bug: #2025219
Change-Id: Iba62e76b3cf83f 3ade6df81288d2d 77129ffc725 0930d1c5481293a 6d2dc8d915)
(cherry picked from commit a0e614ee10937eb