Bug 1787551

Summary: Show incorrect msg if vm migration failed
Product: OpenShift Container Platform Reporter: zhe peng <zpeng>
Component: Console Kubevirt PluginAssignee: Tomas Jelinek <tjelinek>
Status: CLOSED DUPLICATE QA Contact: Nelly Credi <ncredi>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, ipinto
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-15 11:41:22 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:
Description Flags
describe vmi
screenshot of UI none

Description zhe peng 2020-01-03 11:07:16 UTC
Description of problem:
Show incorrect msg if vm migration failed

Version-Release number of selected component (if applicable):
OCP4.3 + CNV2.2

How reproducible:

Steps to Reproduce:
1.create and start vm
2.migrate vm from rhcos to rhel worker
source node:host-172-16-0-23
target node:cnv-executor-zpeng43-rhel-worker-0

3.migrate failed due to CPU issue, check vm status in UI
failed msg:
VirtualMachineInstance migration uid b52efbf0-a356-4e2c-b62f-8f97dce06bb2 failed. reason:Live migration failed virError(Code=9, Domain=31, Message='operation failed: guest CPU doesn't match specification: missing features: umip,arch-capabilities')

Actual results:
migrate failed, but in UI the node is change to

the vm status is "Stopping" for long time

i can use console to connect vm right now because the vm is running on source

Expected results:
if migration failed, need change node to source and set status to running.

Additional info:
#oc get pods
virt-launcher-testvm-m57xf                                        2/2     Running            0          17m
virt-launcher-testvm-z5zwr                                        0/2     Error              0          16m

Comment 1 Tomas Jelinek 2020-01-06 08:47:47 UTC
Can you please also attach the VirtualMachineInstance and the VirtualMachineInstanceMigration objects after the migration failed?

Comment 2 zhe peng 2020-01-07 10:18:57 UTC
Created attachment 1650328 [details]

Comment 3 zhe peng 2020-01-07 10:33:02 UTC
Created attachment 1650329 [details]
describe vmi

Comment 4 zhe peng 2020-01-07 10:41:06 UTC
Created attachment 1650334 [details]
screenshot of UI

Comment 5 Tomas Jelinek 2020-01-15 11:41:22 UTC

*** This bug has been marked as a duplicate of bug 1785344 ***