Bug ID 1634545: OpenShift cluster may fail to install if no management IP's are configured

Last Modified: Apr 20, 2025

Affected Product(s):
F5OS Install/Upgrade, Velos(all modules)

Known Affected Versions:
F5OS-C 1.5.1, F5OS-C 1.6.0, F5OS-C 1.6.1, F5OS-C 1.6.2

Fixed In:
F5OS-C 1.8.0

Opened: Aug 28, 2024

Severity: 2-Critical

Symptoms

The OpenShift cluster may fail to install after a bare-metal install or cluster rebuild if not management IP's have been configured on the system controller management ports. The output of the 'show cluster' command reports that 'MasterInstall' is in a state of Failed. syscon-1-standby# show cluster STAGE NAME STATUS -------------------------------------- AddingBlade Not Started HealthCheck Done HostedInstall Not Started MasterAdditionalInstall Not Started MasterInstall Failed <=========== NodeBootstrap Done NodeJoin Not Started Prerequisites Done RemoveBlade InProgress ServiceCatalogInstall Not Started etcdInstall Done

Impact

OpenShift cluster install will fail until management IP's are configured on the the system controller management ports.

Conditions

No management IP's configured on the system controller management ports while an OpenShift cluster install is initiated, either via a bare-metal install or a manual cluster rebuild.

Workaround

Configure management IP's on the system controller management ports.

Fix Information

F5OS will now add a default route on both system controllers that will allow the OpenShift cluster install to complete even when no management addresses have been configured on the system controller management ports.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips