Bug 877981
Summary: | webadmin: selecting a template will change the cluster selection back to default when there is more than one cluster under the same DC | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Dafna Ron <dron> |
Component: | ovirt-engine-webadmin-portal | Assignee: | Michal Skrivanek <michal.skrivanek> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Belka <jbelka> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.1.0 | CC: | acathrow, dyasny, ecohen, iheim, michal.skrivanek, ofrenkel, Rhev-m-bugs, ykaul |
Target Milestone: | --- | ||
Target Release: | 3.2.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | virt | ||
Fixed In Version: | sf2 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-11 08:19:51 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: | 915537 |
Description
Dafna Ron
2012-11-19 11:13:56 UTC
After the creation of VM template, a cluster and datacenter are assigned to the new template by default. When creating new VM based on the template, after I change the template in the dialog window, the list of clusters is updated according to it and selected cluster in the combo is the one attached to the selected VM template. So, this is probably correct behaviour, but can be misleading. All templates are shown and new VM can be created. But, is it better to filter the list of possible templates based on predefined cluster? It means, show only templates attached to a selected cluster? templates are under a DC not a cluster and we can have several clusters under a single DC. if the template is not available it should be because its not under the DC, hence, if I change a DC the templates shown below will be of that new DC. since both clusters can use the templates we should not refresh the cluster list when we select a template only refresh it if we change a DC Patch sent. Merged upstream: a1c0f148b113aeec3f78c51a252da7f2ddf0bd5e OK, sf4. 3.2 has been released 3.2 has been released |