Bug 1064393
Summary: | When creating new VM in advanced view "Start running on" is blank for the second cluster | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | akotov | ||||||
Component: | ovirt-engine-webadmin-portal | Assignee: | Daniel Erez <derez> | ||||||
Status: | CLOSED ERRATA | QA Contact: | Pavel Novotny <pnovotny> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 3.3.0 | CC: | acathrow, adahms, amureini, derez, dfediuck, ecohen, iheim, jbuchta, mavital, michal.skrivanek, Rhev-m-bugs, sherold, yeylon | ||||||
Target Milestone: | --- | ||||||||
Target Release: | 3.4.0 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | virt | ||||||||
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.
|
Story Points: | --- | ||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2014-06-09 15:04:04 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 1090946 | ||||||||
Attachments: |
|
Description
akotov
2014-02-12 14:17:15 UTC
Created attachment 862317 [details]
correct behavior
Created attachment 862318 [details]
blank dropdown list
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. 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 |