Bug 1294451
Summary: | v2v: webadmin uncaught exception occurs when trying to import VM without selecting cluster. | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Nisim Simsolo <nsimsolo> |
Component: | BLL.Virt | Assignee: | jniederm |
Status: | CLOSED CURRENTRELEASE | QA Contact: | meital avital <mavital> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 3.6.1 | CC: | bugs, hannsj_uhl, mavital, mgoldboi, nsimsolo, stirabos, tjelinek |
Target Milestone: | ovirt-3.6.7 | Flags: | rule-engine:
ovirt-3.6.z+
mgoldboi: planning_ack+ tjelinek: devel_ack+ mavital: testing_ack+ |
Target Release: | 3.6.7.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
It wasn't checked if there is a cluster with matching architecture for imported VMs.
Consequence:
There was no cluster in Cluster dropbox on second page of Import VM dialog when VM selected for import had architecture for which there was no corresponding Cluster in selected Data Center
Fix:
* Split table allowing to select VMs for import shows architecture, format: "vm_name (arch)"
* Selection of VMs is validated:
* The selection may only contain VMs of one architecture
* The selection may only contain VMs of architecture that has at least one architecture corresponding Cluster in selected Data Center
Result:
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-04 12:31:33 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1308609, 1359843 |
Description
Nisim Simsolo
2015-12-28 09:17:13 UTC
*** Bug 1294453 has been marked as a duplicate of this bug. *** Can you follow http://www.ovirt.org/OVirt_Engine_Debug_Obfuscated_UI and get a nicer stack trace? obfuscated symbol map code: zab,com.google.gwt.lang.Cast::dynamicCast(Ljava/lang/Object;I)Ljava/lang/Object;,com.google.gwt.lang.Cast,dynamicCast,com/google/gwt/dev/jjs/intrinsic/com/google/gwt/lang/Cast.java,53,0 After some preliminary investigation it seems that we need to filter the list of available data centers in the very first part of the import process to show only those DCs that have hosts capable of V2V. This will prevent getting into further frontend issues in this inconsistent state and among other things would also cover this scenario with PPC only clusters. Verified on 3.6.7.4-0.1.el6 When trying to continue to second import dialog, the next "operation canceled" message appears: "There is no cluster supporting selected VM(s) architecture in selected Data Center" |