Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1142629

Summary: [Edit VM] > Irrelevant and wrong pop-up Operation canceled while moving VM from cluster to cluster
Product: Red Hat Enterprise Virtualization Manager Reporter: Michael Burman <mburman>
Component: ovirt-engine-webadmin-portalAssignee: Gilad Chaplik <gchaplik>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: alukiano, bazulay, dfediuck, ecohen, eedri, gklein, iheim, ipinto, istein, ofrenkel, ogofen, rbalakri, Rhev-m-bugs, sherold, yeylon
Target Milestone: ---Keywords: AutomationBlocker
Target Release: 3.5.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: sla
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:07:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screen shoot none

Description Michael Burman 2014-09-17 06:56:20 UTC
Created attachment 938356 [details]
Screen shoot

Description of problem:
[Edit VM] > Irrelevant and wrong pop-up Operation canceled while moving VM from cluster to cluster. 
If you try to move VM from cluster to cluster- it can be from same cpu type(intel to intel), or with different cpu type(amd to intel), in both cases you get this message and in both cases operation doesn't really canceled, because the change is done, VM moved to other cluster and you can run the VM. 

Version-Release number of selected component (if applicable):
3.5.0-0.12.beta.el6ev

How reproducible:
always

Steps to Reproduce:
1.Edit VM and move it to other cluster, press 'ok' 
2.
3.

Actual results:
You will get this message: Operation Canceled
Error while executing action:

test1:

    ACTION_TYPE_CPU_PROFILE_NOT_MATCH_CLUSTER

After pressing close button, the VM moved to other cluster and can be run.
So operation doesn't really canceled.

Expected results:
- If i'm trying to move VM from cluster to cluster with same cpu type, i shouldn't see such error. 
- If you trying to move VM from cluster to cluster with different cpu's(amd>intel, or intel>amd)), should i get this message?? what is the right behavior? because as it seems, there is no problem to the VM to run on different cpu's type. And if so, in this case i shouldn't see this error.
- The message about Operation canceled don't really cancel the operation in both cases. Because the change is done in both cases and VM can run after this error message.
Additional info:

Comment 1 Gilad Chaplik 2014-10-28 07:28:55 UTC
*** Bug 1145059 has been marked as a duplicate of this bug. ***

Comment 2 Gilad Chaplik 2014-10-28 07:29:15 UTC
*** Bug 1156018 has been marked as a duplicate of this bug. ***

Comment 3 Roy Golan 2014-11-19 08:52:51 UTC
*** Bug 1158458 has been marked as a duplicate of this bug. ***

Comment 4 Ilanit Stein 2014-11-27 13:12:48 UTC
Eyal,

Look like this fix is already in vt10.1.
Can you please move this bug to on_qa?

Thanks,
Ilanit.

Comment 6 Michael Burman 2014-11-30 07:48:01 UTC
Verified on - 3.5.0-0.22.el6ev

Comment 7 Eyal Edri 2015-02-17 17:07:11 UTC
rhev 3.5.0 was released. closing.