Last Modified: Jan 26, 2026
Affected Product(s):
F5OS Velos
Known Affected Versions:
F5OS-C 1.8.1, F5OS-C 1.8.2
Opened: Sep 02, 2025 Severity: 3-Major
It is possible that after a controller upgrade, the tenant virt-launcher pod can be stuck in ImagePullBackOff state.
The registry containing the KubeVirt images is not synchronized between the controllers, causing the active controller to reference an incorrect registry.
The tenant will not come up.
Issue a controller failover.
None