Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1520119

Summary: [UI] - Cluster's name is <UNKNOWN> on template import in the admin pop up messages(green)
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: Frontend.WebAdminAssignee: Maor <mlipchuk>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: amureini, bugs, michal.skrivanek, mlipchuk
Target Milestone: ovirt-4.2.0Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-20 10:53:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

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.