Bug 1835974
Summary: | [Baremetal] API VIP doesn't fail over to another master when local LB is not healthy. | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Yossi Boaron <yboaron> |
Component: | Installer | Assignee: | Yossi Boaron <yboaron> |
Installer sub component: | OpenShift on Bare Metal IPI | QA Contact: | Eldar Weiss <eweiss> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | augol, jkaur, kgarriso, vvoronko |
Version: | 4.4 | Keywords: | Triaged |
Target Milestone: | --- | ||
Target Release: | 4.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 4.5.0-0.nightly-2020-06-09-050255 | Doc Type: | Bug Fix |
Doc Text: |
Cause:
Failure of the self-hosted Loadbalancer used for distributing OCP API traffic on the master node that serves as API LB frontend (owns the API VIP).
Consequence:
The relevant master node will continue to own the API-VIP IP address although local LB is unhealthy and as a result of that OCP API will be unreachable for ~10 seconds.
Fix:
The Keepalived check for API-VIP script will monitor also self-hosted Loadbalancer health.
Result:
In case of a failure in local self-hosted Loadbalancer in the master node holding the API-VIP the API-VIP will failover to another master-node and we shouldn't hit service downtime for OCP-API.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-13 17:39:04 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Yossi Boaron
2020-05-14 20:05:59 UTC
@Yossi Can you add a severity to this BZ please? Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409 |