Helm Charts are not available when running system application-update for kubevirt
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
New
|
Undecided
|
Unassigned |
Bug Description
Brief Description
When attempting to upgrade KubeVirt using the AppFramework upgrade process (i.e. system application-
Severity
Major
Steps to Reproduce
Install KubeVirt Application from Master Branch:
Use a recent ISO build, which should contain the lastest version of KubeVirt from the master branch.
Verify Successful Installation and Stabilization of KubeVirt:
Ensure that the KubeVirt application installs successfully.
Wait for the application to stabilize, which typically takes around 3 minutes.
Initiate Upgrade Using the Designer Build:
With KubeVirt installed and stable, execute the system application-upgrade command using the designer build.
Expected Behavior
The KubeVirt and CDI, both components of the kubevirt-app, should upgrade successfully. Successful upgrade can be verified by ensuring all pods are running the latest versions: 1.1.0 for KubeVirt and 1.57.0 for CDI.
Actual Behavior
Master branch version of kubevirt installed:
[sysadmin@
+------
| application | version | manifest name | manifest file | status | progress |
+------
| cert-manager | 23.09-72 | cert-manager-
| dell-storage | 23.09-7 | dell-storage-
| kubevirt-app | 23.09-14 | kubevirt-
| nginx-ingress-
| oidc-auth-apps | 23.09-47 | oidc-auth-
| platform-integ-apps | 23.09-126 | platform-
+------
[sysadmin@
Warning: kubevirt.io/v1 VirtualMachineI
NAME READY STATUS RESTARTS AGE
pod/virt-
pod/virt-
pod/virt-
pod/virt-
service/
service/
service/virt-api ClusterIP 10.101.76.196 <none> 443/TCP 2m15s
service/
daemonset.
deployment.
deployment.
deployment.
replicaset.
replicaset.
replicaset.
kubevirt.
[sysadmin@
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /etc/kubernetes
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
cm-cert-manager cert-manager 1 2024-01-16 17:08:35.69711518 +0000 UTC deployed cert-manager-
deployment-manager default 1 2024-01-16 17:11:05.670897014 +0000 UTC deployed wind-river-
dm-monitor platform-
ic-nginx-ingress kube-system 1 2024-01-16 17:07:19.825750451 +0000 UTC deployed ingress-nginx-4.8.2 1.9.3
kubevirt-app kube-system 1 2024-01-17 08:20:52.985657931 +0000 UTC deployed kubevirt-app-0.1.0 1.0.0
stx-ceph-
stx-cephfs-
stx-rbd-provisioner kube-system 1 2024-01-16 17:29:08.868377259 +0000 UTC deployed ceph-csi-rbd-3.9.0 3.9.0
Updating the application I observer errors in the flux-helm controller.
[sysadmin@
[sysadmin@
2024-01-
[sysadmin@
2024-01-
Flux trying to revert the version back (master build), but it's failing because the init container of the master build can't handle the update contents of /var/opt/kubevirt. This is a follow-on effect to the upgrade failure.
[sysadmin@
Warning: kubevirt.io/v1 VirtualMachineI
NAME READY STATUS RESTARTS AGE
pod/virt-
pod/virt-
pod/virt-
pod/virt-
pod/virt-
service/
service/
service/virt-api ClusterIP 10.101.76.196 <none> 443/TCP 13m
service/
daemonset.
deployment.
deployment.
deployment.
replicaset.
replicaset.
replicaset.
replicaset.
replicaset.
replicaset.
Reproducibility
100%
Hi man, any progress? We hit the same issue recently.