Red Hat Bugzilla – Bug 1536300
Live Migration: Engine fails to pass the destination Host parameter when user shuts down VM in the middle of migration
Last modified: 2018-05-15 13:48:17 EDT
Description of problem: When a VM being migrated from Host A to Host B is shutdown manually by a user before the migration completes, although VM status is "Down" , engine fails to pass the destination Host parameter . The VM ends up being in "MigratingTo" state without any associated Host. It fails to let any other operation on it until manual DB intervention. Version-Release number of selected component (if applicable): rhevm-4.1.8.2-0.1.el7.noarch Additional info:
looks like a duplicate of bug 1505399
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.1.z': '?'}', ] For more info please contact: rhv-devops@redhat.comINFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.1.z': '?'}', ] For more info please contact: rhv-devops@redhat.com
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found clone flags: ['rhevm-4.1.z', 'rhevm-4.2-ga'], ] For more info please contact: rhv-devops@redhat.comINFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found clone flags: ['rhevm-4.1.z', 'rhevm-4.2-ga'], ] For more info please contact: rhv-devops@redhat.com
INFO: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [No relevant external trackers attached] For more info please contact: rhv-devops@redhat.com
Verify with: Engine: Software Version:4.2.1.6-0.1.el7 Host: OS Version:RHEL - 7.4 - 18.el7 Kernel Version:3.10.0 - 693.17.1.el7.x86_64 KVM Version:2.9.0 - 16.el7_4.14 LIBVIRT Version:libvirt-3.9.0-8.el7 VDSM Version:vdsm-4.20.17-1.el7ev Steps: 1. Start vm 2. Migration VM 3. While migration start , state "migrateTo" - Stop VM Results: VM stopped, VM not exist on any host.
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, 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/RHEA-2018:1488