Last Modified: Oct 19, 2025
Affected Product(s):
F5OS Velos
Known Affected Versions:
F5OS-C 1.5.1
Fixed In:
F5OS-C 1.8.0
Opened: Sep 20, 2023 Severity: 3-Major
When the controller-manager pods are unable to start and have a status of CrashLoopBackOff, tenants may fail to start. oc get pods -o wide --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE default docker-registry-1-qf79w 1/1 Running 0 4d 100.77.0.44 controller-1.chassis.local <none> default registry-console-1-dflwj 1/1 Running 0 4d 100.77.0.49 controller-1.chassis.local <none> default router-1-cdb9h 1/1 Running 0 4d 100.76.0.43 controller-2.chassis.local <none> default router-1-vtkv6 1/1 Running 0 4d 100.77.0.42 controller-1.chassis.local <none> kube-service-catalog apiserver-5xz4z 1/1 Running 0 147d 100.77.0.46 controller-1.chassis.local <none> kube-service-catalog apiserver-ltnkh 1/1 Running 6 147d 100.76.0.42 controller-2.chassis.local <none> kube-service-catalog controller-manager-hkpz2 0/1 CrashLoopBackOff 8 18m 100.76.0.209 controller-2.chassis.local <none> kube-service-catalog controller-manager-zw9kx 0/1 CrashLoopBackOff 3 1m 100.77.0.240 controller-1.chassis.local <none>
Tenants fail to start.
This issue is caused under the following conditions: - VELOS chassis - Upgrade
Reinstall Openshift.
None