Bug ID 1189013: Race condition in platform bringup can result in incorrect Openshift images in local registry after upgrade

Last Modified: May 29, 2024

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

Known Affected Versions:
F5OS-C 1.5.0

Fixed In:
F5OS-C 1.6.0, F5OS-C 1.5.1

Opened: Nov 11, 2022

Severity: 2-Critical

Symptoms

After upgrade to F5OS-C controller OS version 1.5.x, it is possible for the docker registry from which the Openshift platform pulls container images to have the wrong contents. This can result in necessary images to be missing from the registry, and lead to failures in Openshift cluster bringup after a cluster re-install.

Impact

Openshift cluster does not come up after re-install.

Conditions

Upgrading F5OS-C controller OS from a pre-1.5.x version to 1.5.x and triggering a cluster re-install after upgrade.

Workaround

1. Remove the controller ISO version used to USB install the system. This version can be determined by running the following in a bash shell on either system controller: grep ^version: /var/platform-services/VERSION | cut -d' ' -f2 2. Reboot both system controllers.

Fix Information

Fix for race condition in platform bringup that can result in incorrect Openshift images in local registry after upgrade.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips