Bug ID 1077105: Chassis partition pods may fail to start, with OpenShift cluster status flapping

Last Modified: May 29, 2024

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

Known Affected Versions:
F5OS-C 1.3.1

Fixed In:
F5OS-C 1.3.2

Opened: Jan 31, 2022

Severity: 1-Blocking


Chassis Partition/Tenant pods may fail to start if the partition namespace key is missing or stale. OpenShift cluster status may flap repeatedly on the standby VELOS system controller: Summary Status: Openshift cluster is NOT ready. Openshift cluster is ready.


Partition/Tenant pods may fail to start. OpenShift cluster status observed to be continually flapping on the standby system controller.


Creating a new partition on F5OS-C 1.3.1, which is running-active on the standby system controller.


Fail over the active system controller and ensure the partitions are running-active on the newly active system controller: system redundancy go-standby

Fix Information

This issue is fixed.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips