Bug ID 1061065: After controller upgrade, tenant might not work correctly due to failed install of KubeVirt pods

Last Modified: Dec 07, 2023

Affected Product(s):
F5OS Install/Upgrade(all modules)

Known Affected Versions:
F5OS-C 1.2.2

Fixed In:
F5OS-C 1.3.0

Opened: Nov 11, 2021

Severity: 3-Major

Symptoms

After a system controller upgrade, a tenant might not deploy, because upgraded KubeVirt pods might have failed to install correctly.

Impact

Tenant will not deploy correctly.

Conditions

-- System controllers were recently upgraded. -- KubeVirt pods not installed correctly

Workaround

1. Remove existing KubeVirt pods that are incorrectly installed. 2. Manually edit the kubevirt-velos-install.sh script to point to the correct registry port. 3. Rerun the install script to install the KubeVirt pods correctly.

Fix Information

The kubevirt-velos-install.sh script is now updated to the correct registry port, which enables KubeVirt pods to be updated correctly.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips