Bug ID 1138085: On VELOS, reinstalling OpenShift does not return partition to functional state

Last Modified: Jun 19, 2025

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

Known Affected Versions:
F5OS-C 1.0.0, F5OS-C 1.2.2, F5OS-C 1.3.2, F5OS-C 1.5.0, F5OS-C 1.5.1, F5OS-C 1.6.0, F5OS-C 1.6.1, F5OS-C 1.6.2, F5OS-C 1.8.0, F5OS-C 1.8.1

Opened: Aug 22, 2022

Severity: 4-Minor

Symptoms

When OpenShift is reinstalled on a VELOS system (that is, by running 'touch /var/omd/CLUSTER_REINSTALL'), partition services that run as Kubernetes pods are not re-deployed after the installation finishes.

Impact

Pods are not re-deployed after OpenShift installation finishes.

Conditions

- Partitions enabled on a VELOS system - Reinstall OpenShift

Workaround

If you disable and re-enable the partition(s) that pods are running on, they will be re-deployed. Perform the following steps from the VELOS System Controller Management Command Line Interface: syscon-2-active# config Entering configuration mode terminal syscon-2-active(config)# partitions partition <name of partition> config disabled ; top syscon-2-active(config)# commit Commit complete. syscon-2-active(config)# partitions partition <name of partition> config enabled ; top syscon-2-active(config)# commit Commit complete. syscon-2-active(config)# exit

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips