Bug ID 1042273: ETCD-HA Instance might not initialize correctly after PXE booting the system controller

Last Modified: Dec 07, 2023

Affected Product(s):
F5OS Velos(all modules)

Known Affected Versions:
F5OS-C 1.1.0, F5OS-C 1.1.1, F5OS-C 1.1.2, F5OS-C 1.1.3, F5OS-C 1.1.4

Fixed In:
F5OS-C 1.3.0, F5OS-C 1.2.2

Opened: Aug 23, 2021

Severity: 3-Major

Symptoms

The ETCD-HA instance might not initialize correctly after PXE booting a system controller and re-installing that system controller into the OpenShift cluster. When the instance initializes incorrectly and one of the system controllers is down, the OpenShift API does not operate correctly.

Impact

When the instance initializes incorrectly and one of the system controllers is down, the OpenShift API does not operate correctly.

Conditions

PXE boot of a system controller in a running OpenShift cluster.

Workaround

None

Fix Information

The orchestration-manager now correctly re-initializes the ETCD-HA instance when a system controller is PXE booted and then added to the OpenShift cluster.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips