Loading
kubevirt-test-vms: adding back the VMI healtcheck
What does this MR do and why?
As a follow up over !9879 (merged), it has been seen that the test wkld-update-test-units is failing on the same unit with the same error as before.
Extract from yesterday test:
crustgather-job-17829517075 ~> kubectl --context workload get vm,vmi -n kubevirt-tests -o custom-columns='KIND:.kind,NAME:.metadata.name,GEN:.metadata.generation,OBSGEN:.status.observedGeneration,READY:.status.ready,PHASE:.status.phase,STATUS:.status.printableStatus,PCI_TOPO:.spec.template.metadata.annotations.kubevirt\.io/pci-topology-version'
KIND NAME GEN OBSGEN READY PHASE STATUS PCI_TOPO
VirtualMachine cirros-kubevirt-vm 3 1 true <none> Running v3
VirtualMachine multus-kubevirt-vm 3 1 true <none> Running v2
VirtualMachineInstance cirros-kubevirt-vm 9 <none> <none> Running <none> <none>
VirtualMachineInstance multus-kubevirt-vm 8 <none> <none> Running <none> <none>Same as today:
crustgather-job-17855150265 ~> kubectl --context workload get vm,vmi -n kubevirt-tests -o custom-columns='KIND:.kind,NAME:.metadata.name,GEN:.metadata.generation,OBSGEN:.status.observedGeneration,READY:.status.ready,PHASE:.status.phase,STATUS:.status.printableStatus,PCI_TOPO:.spec.template.metadata.annotations.kubevirt\.io/pci-topology-version'
KIND NAME GEN OBSGEN READY PHASE STATUS PCI_TOPO
VirtualMachine cirros-kubevirt-vm 3 1 true <none> Running v3
VirtualMachine multus-kubevirt-vm 3 1 true <none> Running v2
VirtualMachineInstance cirros-kubevirt-vm 9 <none> <none> Running <none> <none>
VirtualMachineInstance multus-kubevirt-vm 9 <none> <none> Running <none> <none>
crustgather-job-17855150265 ~>This is happening because the VMI object is not in the inventory of Flux and this is why the wait parameter is not influencing the test
crustgather-job-17855150265 ~> kubectl --context management get ks kubevirt-test-vms -n rke2-capm3-virt -o jsonpath='{range .status.inventory.entries[*]}{.id}{"\n"}{end}'
_kubevirt-tests__Namespace
kubevirt-tests_my-bridge_k8s.cni.cncf.io_NetworkAttachmentDefinition
kubevirt-tests_cirros-kubevirt-vm_kubevirt.io_VirtualMachine
kubevirt-tests_multus-kubevirt-vm_kubevirt.io_VirtualMachine
crustgather-job-17855150265 ~>Related reference(s)
Test coverage
CI configuration
Below you can choose test deployment variants to run in this MR's CI.
Click to open to CI configuration
Legend:
| Icon | Meaning | Available values |
|---|---|---|
| Infra Provider | capd, capo, capm3 |
|
| Bootstrap Provider | kubeadm (alias kadm), rke2, okd, ck8s |
|
| Node OS | ubuntu, suse, na, leapmicro |
|
| Deployment Options | Deployment option list and description | |
| Pipeline Scenarios | Available scenario list and description | |
| Enabled units | Any available units name, by default apply to management and workload cluster. Can be prefixed by mgmt: or wkld: to be applied only to a specific cluster type |
|
| Disabled units | Any available units name, by default apply to management and workload cluster. Can be prefixed by mgmt: or wkld: to be applied only to a specific cluster type |
|
| Target platform | Can be used to select specific deployment environment Available platform list and description | |
| Workload deployment workflow | legacy (default; direct workload-cluster apply) or gitops (deploy workload cluster through the GitOps-managed flow) |
|
| Pipeline control | autorun, manual or blocking. Can be used to override global config and start a deployment pipeline the required way |
-
🎬 preview☁️ capd🚀 kadm🐧 ubuntu -
🎬 preview☁️ capo🚀 rke2🐧 suse -
🎬 preview☁️ capm3🚀 rke2🐧 ubuntu -
☁️ capd🚀 kadm🛠️ light-deploy🐧 ubuntu -
☁️ capd🚀 rke2🛠️ light-deploy🐧 suse -
☁️ capo🚀 rke2🐧 suse -
☁️ capo🚀 rke2🐧 leapmicro -
☁️ capo🚀 kadm🐧 ubuntu -
☁️ capo🚀 kadm🐧 ubuntu🔀 gitops -
☁️ capo🚀 kadm🐧 ubuntu🟢 neuvector,mgmt:harbor -
☁️ capo🚀 rke2🎬 rolling-update🛠️ ha🐧 ubuntu -
☁️ capo🚀 kadm🎬 sylva-upgrade🛠️ ha,misc🐧 ubuntu -
☁️ capo🚀 rke2🎬 rolling-update-no-wkld🛠️ ha🐧 suse -
☁️ capo🚀 rke2🎬 sylva-upgrade🛠️ ha🐧 ubuntu -
☁️ capo🚀 rke2🎬 sylva-upgrade-from-1.6.x🛠️ ha,misc🐧 ubuntu -
☁️ capo🚀 rke2🛠️ ha,misc🐧 ubuntu -
☁️ capo🚀 rke2|okd🎬 no-update🐧 ubuntu|na -
☁️ capo🚀 rke2🛠️ misc🐧 ubuntu🟢 mgmt:harbor🔴 neuvector -
☁️ capo🚀 rke2🛠️ ha,misc,openbao🐧 suse -
☁️ capo🚀 rke2🐧 suse🎬 upgrade-from-prev-tag -
☁️ capm3🚀 rke2🐧 suse -
☁️ capm3🚀 kadm🐧 ubuntu -
☁️ capm3🚀 rke2🛠️ external-openbao-no-tls🐧 ubuntu -
☁️ capm3🚀 rke2🛠️ external-openbao🐧 suse -
☁️ capm3🚀 kadm🛠️ external-openbao,openbao-namespace🐧 ubuntu -
☁️ capm3🚀 ck8s🐧 ubuntu -
☁️ capm3🚀 kadm🎬 rolling-update-no-wkld🛠️ ha,misc🐧 ubuntu -
☁️ capm3🚀 rke2🎬 wkld-k8s-upgrade🛠️ ha🐧 suse -
☁️ capm3🚀 kadm🎬 rolling-update🛠️ ha🐧 ubuntu -
☁️ capm3🚀 rke2🎬 upgrade-from-prev-release-branch🛠️ ha🐧 suse -
☁️ capm3🚀 rke2🛠️ misc,ha🐧 suse -
☁️ capm3🚀 rke2🎬 sylva-upgrade🛠️ ha,misc🐧 suse -
☁️ capm3🚀 kadm🎬 rolling-update🛠️ ha🐧 suse -
☁️ capm3🚀 ck8s🎬 rolling-update🛠️ ha🐧 ubuntu -
☁️ capm3🚀 rke2|okd🎬 no-update🐧 ubuntu|na -
☁️ capm3🚀 rke2🐧 suse🎬 upgrade-from-release-1.5 -
☁️ capm3🚀 rke2🐧 suse🎬 upgrade-to-main
Global config for deployment pipelines
-
autorun pipelines
-
allow failure on pipelines
-
record sylvactl events
Notes:
- Enabling
autorunwill make deployment pipelines to be run automatically without human interaction - Disabling
allow failurewill make deployment pipelines mandatory for pipeline success. - if both
autorunandallow failureare disabled, deployment pipelines will need manual triggering but will be blocking the pipeline
Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.