Bug 1590911
Summary: | wrong template details shown when names are matching | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Evgheni Dereveanchin <ederevea> |
Component: | Frontend.WebAdmin | Assignee: | Liran Rotenberg <lrotenbe> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Tamir <tamir> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.2.3.5 | CC: | bugs, lleistne, lrotenbe, michal.skrivanek, rbarry, rdlugyhe, smelamud, tamir |
Target Milestone: | ovirt-4.4.0 | Flags: | pm-rhel:
ovirt-4.4+
|
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, if two or more templates had the same name, selecting any of these templates displayed the same details from only one of the templates. This happened because the Administration Portal identified the selected template using a non-unique template name. The current release fixes this issue by using the template ID, which is unique, instead.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-20 20:01:53 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: |
Description
Evgheni Dereveanchin
2018-06-13 15:57:13 UTC
Re-targeting to 4.3.1 since it is missing a patch, an acked blocker flag, or both The same issue is with subversions of template. The links from templates goes always to one subversion. There is a similar bug with two clusters in different datacenters having the same name. I verified the fix, the steps: 1. create 2 data centers in oVirt: dc1 and dc2 2. create template "centos7" in both datacenters 3. in admin portal, go to Compute > Templates 4. click on the name of the template in dc2 This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |