Bug 1317526 - v2v: webadmin import dialog should block the option to use 3.5 host.
Summary: v2v: webadmin import dialog should block the option to use 3.5 host.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 3.6.3.3
Hardware: Unspecified
OS: Unspecified
high
medium vote
Target Milestone: ---
: ---
Assignee: jniederm
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-14 13:14 UTC by Nisim Simsolo
Modified: 2021-11-15 13:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-23 12:06:19 UTC
oVirt Team: Virt


Attachments (Terms of Use)
hosts screenshot (120.61 KB, image/png)
2016-03-14 13:19 UTC, Nisim Simsolo
no flags Details
import dialog (39.83 KB, image/png)
2016-03-14 13:19 UTC, Nisim Simsolo
no flags Details
engine log (issue started at: 2016-03-14 14:37:03,990) (233.53 KB, application/x-gzip)
2016-03-14 13:20 UTC, Nisim Simsolo
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-44024 0 None None None 2021-11-15 13:31:28 UTC

Description Nisim Simsolo 2016-03-14 13:14:54 UTC
Description of problem:
1. When using webadmin import dialog, the option to select 3.5 host as a proxy host should be blocked.
2. When using webadmin import dialog, the option to select "any host in data center" when there are no 3.6 hosts on that DC should be blocked.

Currently, when trying to load VMware VMs using 3.5 host, the next failure message displayed on import dialog: 
"Failed to communicate with the external provider, see log for additional details"

Version-Release number of selected component (if applicable):
rhevm-3.6.3.4-0.1.el6
3.5 host:
vdsm-4.16.36-1.el7ev.x86_64
libvirt-1.2.17-13.el7_2.3.x86_64
qemu-kvm-rhev-2.3.0-31.el7_2.7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Using rhevm 3.6, Create DC with 3.5 compatibility. Under that DC create cluster with 3.5 compatibility. Add 3.5 host to that cluster.
2. Navigate to virtual machines tab --> import
3. Select 3.5 compatible DC, VMware source, set VMware details and click on "proxy host" dropbox.
4. Select one of the options listed in the dropbox and click "load" button.

Actual results:
3.5 host and "any host in data center" options are listed in dropbox.

Expected results:
- "proxy host" dropbox should not list anything since the host is 3.5 and there are no other 3.6 hosts under that DC.
- The next failure message displayed in the dialog: "Failed to communicate with the external provider, see log for additional details"
- The next ERROR logged in engine.log: 
"2016-03-14 14:46:17,517 ERROR [org.ovirt.engine.core.bll.GetVmsFromExternalProviderQuery] (ajp-/127.0.0.1:8702-16) [] Exception: org.ovirt.engine.core.common.errors.EngineException: EngineException: org.ovirt.engine.core.vdsbroker.vdsbrok
er.VDSErrorException: VDSGenericException: VDSErrorException: Failed to GetVmsFromExternalProviderVDS, error = The method does not exist / is not available., code = -32601 (Failed with error unexpected and code 16)
"

Additional info:
Screenshots and engine log attached.

Comment 1 Nisim Simsolo 2016-03-14 13:19:23 UTC
Created attachment 1136144 [details]
hosts screenshot

Comment 2 Nisim Simsolo 2016-03-14 13:19:45 UTC
Created attachment 1136145 [details]
import dialog

Comment 3 Nisim Simsolo 2016-03-14 13:20:27 UTC
Created attachment 1136146 [details]
engine log (issue started at: 2016-03-14 14:37:03,990)

Comment 4 Tomas Jelinek 2016-03-23 11:09:19 UTC
it seems as the fix should be similar to https://bugzilla.redhat.com/show_bug.cgi?id=1294451 
setting same milestones.

Comment 5 Michal Skrivanek 2016-06-23 12:06:19 UTC
nacked for 3.6, not required in 4.0, closing then


Note You need to log in before you can comment on or make changes to this bug.