Bug 1064393 - When creating new VM in advanced view "Start running on" is blank for the second cluster
Summary: When creating new VM in advanced view "Start running on" is blank for the sec...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.4.0
Assignee: Daniel Erez
QA Contact: Pavel Novotny
URL:
Whiteboard: virt
Depends On:
Blocks: rhev3.4snapshot2
TreeView+ depends on / blocked
 
Reported: 2014-02-12 14:17 UTC by akotov
Modified: 2019-04-28 09:58 UTC (History)
13 users (show)

Fixed In Version: av5
Doc Type: Bug Fix
Doc Text:
Previously, selecting the host on which a virtual machine is to start running via the Host tab of the New Virtual Machine and Edit Virtual Machine windows and changing the Cluster in which the virtual machine is to run would result in no host in the selected cluster being selected as the host on which the virtual machine is to run. This was caused by the logic used to select a default host within the cluster, which would leave the selected option blank if a host of the same name was not present in the newly selected cluster. Now, this logic has been revised so that even if there is no host of the same name in the newly selected cluster, one of the hosts in that cluster will be selected instead.
Clone Of:
Environment:
Last Closed: 2014-06-09 15:04:04 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
correct behavior (47.40 KB, image/jpeg)
2014-02-12 14:17 UTC, akotov
no flags Details
blank dropdown list (52.15 KB, image/jpeg)
2014-02-12 14:18 UTC, akotov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:0506 0 normal SHIPPED_LIVE Moderate: Red Hat Enterprise Virtualization Manager 3.4.0 update 2014-06-09 18:55:38 UTC
oVirt gerrit 24077 0 None None None Never
oVirt gerrit 25862 0 None None None Never

Description akotov 2014-02-12 14:17:15 UTC
Description of problem:

When creating new VM and selecting advanced view Run on host is selected by default, but when switching to another cluster user has to change value from blank to the specific host.

Version-Release number of selected component (if applicable):

Red Hat Enterprise Virtualization Manager Version: 3.3.0-0.46.el6ev

Expected results:

If only one host is available in the second cluster it should be chosen by default. Actually, i don't see sense in blank value even for >1 hosts.


Refer to screenshots new1 and new2 for reference

Comment 1 akotov 2014-02-12 14:17:47 UTC
Created attachment 862317 [details]
correct behavior

Comment 2 akotov 2014-02-12 14:18:21 UTC
Created attachment 862318 [details]
blank dropdown list

Comment 6 Pavel Novotny 2014-04-01 16:38:54 UTC
Verified in rhevm-3.4.0-0.12.beta2.el6ev.noarch (av5).

Verification steps:

Approach 1 - hosts in different clusters:
1. Create data center DC with clusters Cluster1 and Cluster2.
2. Add host Host1 to Cluster1 and Host2 to Cluster2.
3. On VMs tab open New VM dialog. In Cluster select box should be value DC/Cluster1.
   ==> In Host / Start Running On - Specific should be already chosen value Host1. No other value (like blank) can be picked.
4. Switch Cluster to DC/Cluster2.
   ==> In Host / Start Running On - Specific the value should change to Host2. No other value (like blank) can be picked.

Approach 2 - hosts in same cluster:
1. Create data center DC with cluster Cluster1.
2. Add hosts Host1 and Host2 to Cluster1.
3. On VMs tab open New VM dialog. In Cluster select box should be value DC/Cluster1.
   ==> In Host / Start Running On - Specific should be already chosen value Host1. Or you can pick Host2 (but no blank value is present).

The only time blank value can be chosen in the Host / Specific select box is when a cluster doesn't contain any hosts. But then the VM dialog validation doesn't allow to submit it anyway.

Comment 7 errata-xmlrpc 2014-06-09 15:04:04 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2014-0506.html


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