Bug 1792870

Summary:	[RFE] Display cluster ID in cluster view
Product:	[oVirt] ovirt-engine	Reporter:	Jan Zmeskal <jzmeskal>
Component:	Frontend.WebAdmin	Assignee:	Lucia Jelinkova <ljelinko>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ivana Saranova <isaranov>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	future	CC:	ahadas, bugs, lleistne, sgratch
Target Milestone:	ovirt-4.4.3	Keywords:	FutureFeature
Target Release:	---	Flags:	pm-rhel: ovirt-4.4? pm-rhel: ovirt-4.5? pm-rhel: planning_ack? pm-rhel: devel_ack+ lleistne: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.3.5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-11 06:41:59 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 Jan Zmeskal 2020-01-20 09:43:55 UTC

Description of problem:
When you open cluster view in webadmin, cluster ID is not visible there. However, as far as I'm aware, most other resources expose their ID this way (storage domain, template, VM, etc.). To obtain cluster ID, you need to go to REST API and find it there. I believe such a change should be quite easy to implement and it eases users' life if they need to use cluster ID e.g. during scripting.


Version-Release number of selected component (if applicable):
4.3.8.2

How reproducible:
100 %

Steps to Reproduce:
1. Open webadmin
2. Find some random cluster
3. Open the cluster view

Actual results:
Cluster ID is not exposed there

Expected results:
Cluster ID should be exposed in UI the same way VM ID, Template ID and others are visible.

Comment 1 Ivana Saranova 2020-10-02 23:28:19 UTC

Steps:
1. Open webadmin
2. Find some random cluster
3. Open the cluster view

Results:
Cluster detail view now contains a Cluster ID.

Verified in:
ovirt-engine-4.4.3.5-0.5.el8ev.noarch

Comment 2 Sandro Bonazzola 2020-11-11 06:41:59 UTC

This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.3 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.