Bug 1520119 - [UI] - Cluster's name is <UNKNOWN> on template import in the admin pop up messages(green)
Summary: [UI] - Cluster's name is <UNKNOWN> on template import in the admin pop up mes...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ovirt-4.2.0
: ---
Assignee: Maor
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-03 09:05 UTC by Michael Burman
Modified: 2017-12-20 10:53 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.2.0
Clone Of:
Environment:
Last Closed: 2017-12-20 10:53:49 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)
screenshot (61.17 KB, image/png)
2017-12-03 09:05 UTC, Michael Burman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 85020 0 master MERGED core: Add cluster name to import template job 2017-12-03 23:46:04 UTC

Description Michael Burman 2017-12-03 09:05:22 UTC
Created attachment 1362200 [details]
screenshot

Description of problem:
[UI] - Cluster's name is <UNKNOWN> on template import in the admin pop up messages(green).

When importing VM or template from a data domain, green admin messages are shown in the webadmin UI letting the admin/user know that operation succeeded.
On VM import, the message shows the correct cluster destination name, but
on Template import, the cluster name is <UNKNOWN>. 


Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20171201121510.gitb338573.el7.centos

How reproducible:
100%

Steps to Reproduce:
1. Import template from data domain 

Actual results:
Finished importing Template 'template_name' from configuration to Cluster <UNKNOWN>

Expected results:
Cluster's name

Additional info:
On VM import the admin message is fine.

Comment 1 Sandro Bonazzola 2017-12-12 16:08:13 UTC
This bug is targeted 4.2.1 but is modified in 4.2.0.
Can you please check / verify this bug status and set target milestone and bug status accordingly?

Comment 2 Allon Mureinik 2017-12-12 17:14:13 UTC
(In reply to Sandro Bonazzola from comment #1)
> This bug is targeted 4.2.1 but is modified in 4.2.0.
> Can you please check / verify this bug status and set target milestone and
> bug status accordingly?
This patch is included in the ovirt-engine-4.2.0 tag.

Comment 3 Michael Burman 2017-12-13 06:48:32 UTC
Verified on - 4.2.1-0.0.master.20171211205712.git7b1f4d1.el7.centos
and 4.2.0.2-0.1.el7

Comment 4 Sandro Bonazzola 2017-12-20 10:53:49 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

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


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