Bug ID 1071693: KubeVirt pods might fail when upgrading from F5OS-C v1.2.1 to v1.3.0

Last Modified: Apr 22, 2022

Bug Tracker

Affected Product:  See more info
F5OS Install/Upgrade(all modules)

Known Affected Versions:
1.3.0

Fixed In:
1.3.1

Opened: Jan 06, 2022
Severity: 2-Critical

Symptoms

During a system controller upgrade from F5OS-C v1.2.1 to v1.3.0, the KubeVirt pods fail to upgrade and produce an error causing the tenant to not operate properly.

Impact

The KubeVirt images are not available on the VELOS system controller registry. and the tenant does not operate properly because it relies on KubeVirt pods to be installed correctly.

Conditions

Upgrading from F5OS-C v1.2.1 to v1.3.0.

Workaround

Follow these steps on the active VELOS system controller: 1. cp /usr/share/omd/kubevirt/omd-kubevirt-velos-install.sh /tmp 2. cd /tmp vi omd-kubevirt-velos-install.sh 3. Add these lines at line 99 of that file: else echo "Using registry port of $official_port for kubevirt install" echo "Update registry port in kubevirt yml files" sed -i -e "s@:[0-9][0-9][0-9][0-9]/@:$official_port/@" $WORKDIR/kubevirt-velos.yaml 4. In one Linux shell window: oc delete -f /usr/share/omd/kubevirt/kubevirt-velos.yaml 5. In another Linux shell window: /tmp/omd-kubevirt-velos-install.sh /usr/share/omd/kubevirt/

Fix Information

This issue is resolved.

Behavior Change