Bug 1939987
| Summary: | Live Migrating a PAUSED VM gets it into UNPAUSED state on the migrated node | ||
|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Kedar Bidarkar <kbidarka> |
| Component: | Virtualization | Assignee: | Vladik Romanovsky <vromanso> |
| Status: | CLOSED ERRATA | QA Contact: | Kedar Bidarkar <kbidarka> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 2.6.0 | CC: | cnv-qe-bugs, lpivarc, sgott, vromanso |
| Target Milestone: | --- | ||
| Target Release: | 4.8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virt-operator-container-v4.8.0-60 hco-bundle-registry-container-v4.8.0-375 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-07-27 14:28:41 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Re-targetting this to the current release as it made it in. To verify, follow steps to reproduce in description. Summary: Paused VMI now remains in Paused state even after the Live-Migration. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Virtualization 4.8.0 Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2920 |
Description of problem: [kbidarka@localhost nfs]$ oc get vmi -o wide NAME AGE PHASE IP NODENAME LIVE-MIGRATABLE PAUSED vm-nfs-rhel83 3m7s Running xxx.yyy.zzz.129 infra-07.redhat.com True [kbidarka@localhost nfs]$ virtctl pause vmi vm-nfs-rhel83 VMI vm-nfs-rhel83 was scheduled to pause [kbidarka@localhost nfs]$ oc get vmi -o wide NAME AGE PHASE IP NODENAME LIVE-MIGRATABLE PAUSED vm-nfs-rhel83 3m26s Running xxx.yyy.zzz.129 infra-07.redhat.com True True [kbidarka@localhost migration]$ oc apply -f migration-pause-unpause-live-migrate.yaml virtualmachineinstancemigration.kubevirt.io/job11-pause-unpause-live-migrate2 created [kbidarka@localhost migration]$ oc get vmi NAME AGE PHASE IP NODENAME vm-nfs-rhel83 4m21s Running xxx.yyy.zzz.129 infra-07.redhat.com [kbidarka@localhost migration]$ oc get vmi -o wide NAME AGE PHASE IP NODENAME LIVE-MIGRATABLE PAUSED vm-nfs-rhel83 4m27s Running xxx.yyy.zzz.16 infra-06.redhat.com True [kbidarka@localhost migration]$ oc get pods NAME READY STATUS RESTARTS AGE virt-launcher-vm-nfs-rhel83-sc5hz 0/1 Completed 0 4m40s virt-launcher-vm-nfs-rhel83-t2kxx 1/1 Running 0 24s [kbidarka@localhost migration]$ oc rsh virt-launcher-vm-nfs-rhel83-t2kxx sh-4.4# virsh list --transient Id Name State -------------------- sh-4.4# virsh list --persistent Id Name State --------------------------------------- 1 default_vm-nfs-rhel83 running sh-4.4# exit exit Version-Release number of selected component (if applicable): Tested with CNV-2.6.0 How reproducible: Always Steps to Reproduce: 1.Create and Start a Live-Migratable VM 2. Pause the VMI and Live Migrate it 3. Actual results: VMI is in UNPAUSED state, on the Migrated node Expected results: VMI should remain in PAUSED state, after the Migration. Additional info: Live Migration could happen unintentionally too, that is via a Node Drain, Descheduler or other things, so expect a Paused VM/VMI to remain in Paused state even after Live Migration.