[backport v1.2] [ENHANCEMENT] Bump KubeVirt to 1.1.0-150500.8.6.1

[harvesterhci-io-github-bot]

backport the issue #4758

[harvesterhci-io-github-bot]

Pre Ready-For-Testing Checklist

• [ ] ~If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted?~

• [X] Where is the reproduce steps/test steps documented? The reproduce steps/test steps are at: https://github.com/harvester/harvester/pull/4787, https://github.com/harvester/harvester/pull/5054

• [ ] ~Is there a workaround for the issue? If so, where is it documented?~

• [X] Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)? https://github.com/harvester/harvester/pull/4849 https://github.com/harvester/harvester/pull/5054

  • [X] Does the PR include the explanation for the fix or the feature? yes

  • [X] Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart? The PR for the YAML change is at: https://github.com/harvester/harvester/pull/4849, https://github.com/harvester/harvester/pull/5054 The PR for the chart change is at: https://github.com/harvester/harvester/pull/4849, https://github.com/harvester/harvester/pull/5054

• [ ] ~If labeled: area/ui Has the UI issue filed or ready to be merged?~

• [ ] ~If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged?~

• [ ] If NOT labeled: not-require/test-plan Has the e2e test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue?

  • The automation skeleton PR is at:
  • The automation test case PR is at:

• [ ] If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility? The compatibility issue is filed at:

[TachunLin]

Verified on v1.2-ba51e92e-head (24/03/29) and v1.2-ba51e92e-head (24/04/11)

Result

$\color{green}{\textsf{PASS}}$ to **upgrade** from v1.2.1 to v1.2-head $~~$

* Upgrade stuck in `Upgrading System Service` in the first trial - #5507  * The second trial can successfully upgrade from v1.2.1 to v1.2-head 

$\color{green}{\textsf{PASS}}$ KubeVirt bumped to 1.1.0-150500.8.6.1 after **upgrade** from v1.2.1 to v1.2-head $~~$

``` node1:~ # ctr -n k8s.io image ls | grep virt-operator registry.suse.com/suse/sles/15.5/virt-operator:1.1.0-150500.8.6.1 application/vnd.docker.distribution.manifest.v2+json sha256:6a1b32dd2e1732c587c15f3673ea97317a6210735425d50072f1f146eed6a398 181.1 MiB linux/amd64 io.cri-containerd.image=managed ```

$\color{green}{\textsf{PASS}}$ KubeVirt bumped to 1.1.0-150500.8.6.1 after **fresh install** Harvester cluster $~~$

``` harvester-htp8t:~ # ctr -n k8s.io image ls | grep virt-operator registry.suse.com/suse/sles/15.5/virt-operator:1.1.0-150500.8.6.1 application/vnd.docker.distribution.manifest.v2+json sha256:6a1b32dd2e1732c587c15f3673ea97317a6210735425d50072f1f146eed6a398 181.1 MiB linux/amd64 io.cri-containerd.image=managed ```

$\color{red}{\textsf{Failed}}$ Volume backend automation test $~~$

* $\color{green}{\textsf{PASS}}$ the following volumes backend automation test plans $~~$ - test_create_volume[New-json] - test_create_volume[New-yaml] - test_create_volume[VM Image-json] - test_create_volume[VM Image-yaml] - test_delete_volume_on_existing_vm * $\color{red}{\textsf{Failed}}$ the following volumes backend automation test plans $~~$ - test_delete_volume_on_deleted_vm

$\color{green}{\textsf{PASS}}$ Volume manual test plans $~~$

* $\color{green}{\textsf{PASS}}$ the following volumes manual test plans $~~$ - [Create image from Volume(e2e_fe)](https://harvester.github.io/tests/manual/volumes/create-image-from-volume/) - [Create Volume root disk blank Form with label](https://harvester.github.io/tests/manual/volumes/create-volume-root-disk-blank-form-label/) - [Create volume root disk VM Image Form with label](https://harvester.github.io/tests/manual/volumes/create-volume-root-disk-vm-image-form-label/) - [Create volume root disk VM Image Form(e2e_fe)](https://harvester.github.io/tests/manual/volumes/create-volume-root-disk-vm-image-form/) - [Delete volume that is not attached to a VM (e2e_be_fe)](https://harvester.github.io/tests/manual/volumes/delete-volume-that-is-not-attached-to-vm/) - [Delete volume that was attached to VM but now is not](https://harvester.github.io/tests/manual/volumes/delete-volume-that-was-attached-to-vm-but-is-not-now/) - [Detach volume from virtual machine (e2e_fe)](https://harvester.github.io/tests/manual/volumes/detach-volume-from-virtual-machine/) - [Edit volume increase size via form (e2e_fe) ](https://harvester.github.io/tests/manual/volumes/edit-volume-increase-size-form/) - [Edit volume increase size via YAML (e2e_be)](https://harvester.github.io/tests/manual/volumes/edit-volume-increase-size-yaml/) - [Negative delete Volume that is in use (e2e_be)](https://harvester.github.io/tests/manual/volumes/negative-delete-volume-that-is-in-use/) - [Validate volume shows as in use when attached (e2e_be)](https://harvester.github.io/tests/manual/volumes/validate-volume-shows-in-use-while-attached/)

$\color{green}{\textsf{PASS}}$ VM backend automation test $~~$

* $\color{green}{\textsf{PASS}}$ the following volumes backend automation test plans $~~$ - test_minimal_vm - TestVMOperations::test_pause - TestVMOperations::test_unpause - TestVMOperations::test_stop - TestVMOperations::test_start - TestVMOperations::test_restart - TestVMOperations::test_softreboot - TestVMOperations::test_migrate - TestVMOperations::test_abort_migrate - TestVMOperations::test_delete - test_create_stopped_vm - TestVMResource::test_create_schedule_on_maximum[cpu] - TestVMResource::test_create_schedule_on_maximum[memory] - TestVMResource::test_update_schedule_on_maximum[cpu] - TestVMResource::test_update_schedule_on_maximum[memory] - TestVMResource::test_update_enable_usb - TestVMResource::test_update_enable_user_data - test_create_vm_no_available_resources[cpu] - test_create_vm_no_available_resources[mem] - test_create_vm_no_available_resources[disk] - test_create_vm_no_available_resources[mem-and-cpu] - test_create_vm_no_available_resources[mem-cpu-and-disk] - test_vm_with_bogus_vlan * $\color{red}{\textsf{Failed}}$ the following volumes backend automation test plans $~~$ - TestVMResource::test_update_cpu (access credential) - TestVMClone::test_clone_running_vm (access credential) - TestVMClone::test_clone_stopped_vm (access credential) - test_create_with_existing_volume (access credential) - test_update_vm_machine_type[q35_to_pc] (known issue) - test_update_vm_machine_type[pc_to_q35] (known issue) - TestHotPlugVolume::test_add (access credential)

$\color{red}{\textsf{Failed}}$ VM manual test plans $~~$

* $\color{green}{\textsf{PASS}}$ the following volumes backend automation test plans $~~$ - Basic VM operation: Create / Stop / Start / Restart / Delete - [Chain VM templates and images](https://harvester.github.io/tests/manual/virtual-machines/760-chained-vm-templates/) - [Check VM creation required-fields](https://harvester.github.io/tests/manual/virtual-machines/1283-vm-creation-required-fields/) - [Clone VM that is turned on](https://harvester.github.io/tests/manual/virtual-machines/clone-vm-that-is-turned-on/) - [Clone VM that is turned off](https://harvester.github.io/tests/manual/virtual-machines/clone-vm-that-is-turned-off/) - Take vm backup - Take vm snapshot - Restore vm backup to replace existing - Restore vm backup to create new - Restore vm from snapshot - Clone vm with volume data - Migrate vm to other node - Add volumes to existing vm - Edit yaml of vm - Create vm from node selector on specific node - Create vm from node selector using node label - Edit the vm, change the cpu and memory size - Edit the vm, increase the volume size - Add basic and ssh authentication - Create qc35 machine type vm - Create pc-qc35 machine type vm * $\color{red}{\textsf{Failed}}$ the following volumes backend automation test plans $~~$ - View log function #5266

Test Information

• Test Environment: Four nodes harvester on baremetal machines and single node kvm machine
• Harvester version: v1.2-ba51e92e-head (24/03/29) and v1.2-ba51e92e-head (24/04/11)

Verify Steps

Check can upgrade from v1.2.1 to v1.2-head

Check the KubeVirt can be bumped to 1.1.0-150500.8.6.1 after upgrade complete or fresh installation

1. Execute command `ctr -n k8s.io image ls | grep virt-operator`

Basic volume operation test

1. Run backend automation tests `test_volume.py` on internal E2E Jenkins jobs 2. Run manual test plan to validate basic user operations

Basic vm operation test

1. Run backend automation tests `test_vm.py` and `test_vm_function.py` on internal E2E Jenkins jobs 2. Run manual test plan to validate basic user operations

[TachunLin]

Test result summary

1. The KubeVirt can be bumped to 1.1.0-150500.8.6.1 in a fresh install or upgrade path to v1.2-head

2. We can upgrade from v1.2.1 to v1.2-head,

   • We need to shutdown all VMs before triggering the upgrade Since the vm live migration known issue #5076,

3. Can pass most of the volume and vm operation backend e2e test.

   • Except the case test_delete_volume_on_deleted_vm, double check the similar test steps works on the volume manual test plan Delete volume that is not attached to a VM (e2e_be_fe)

4. Failed the vm manual test plan of all the view log function,

   • Track in the related issue, suppose not related to the bumped kubevirt

     5597

According to the test result. Close this backport issue enhancement.