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

Bug 1145059

Summary: [UI] unreadable Error messege,when editing vm to an incompatible cluster
Product: Red Hat Enterprise Virtualization Manager Reporter: Ori Gofen <ogofen>
Component: ovirt-engine-webadmin-portalAssignee: Gilad Chaplik <gchaplik>
Status: CLOSED DUPLICATE QA Contact: Nikolai Sednev <nsednev>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: acanan, dfediuck, ecohen, gklein, iheim, lsurette, mavital, ofrenkel, ogofen, rbalakri, Rhev-m-bugs, sherold, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sla
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-28 07:28:55 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
images none

Description Ori Gofen 2014-09-22 09:56:44 UTC 
Description of problem:
When attempting to edit Vm's cluster, to another cluster with incompatible type
we receive code instead of a human readable message (see image).
 
Version-Release number of selected component (if applicable):
vt3.1

How reproducible:
100%


Steps to Reproduce:
1.have dc with 2 different clusters
2.add vm on one of them,edit "clusters"


Actual results:
unreadable error message

Expected results:
human readable error message

Additional info:
Comment 1 Ori Gofen 2014-09-22 09:57:30 UTC 
Created attachment 939951 [details]
images
Comment 2 Ori Gofen 2014-09-22 10:20:20 UTC 
*** Bug 1145058 has been marked as a duplicate of this bug. ***
Comment 3 Gilad Chaplik 2014-09-23 12:01:38 UTC 
Ori,

Will fix the untranslated error, but I'm interested how you got it from the UI,
what is 'incompatible type'?

Thanks!
Comment 4 Ori Gofen 2014-09-23 13:46:53 UTC 
Well, what I had was two clusters with different compatibility version (3.4,3.5).
but now I see that this operation fails regardless to compatibility.
Comment 5 Gilad Chaplik 2014-10-28 07:28:55 UTC 

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