Bug 1825020

Summary:	[RFE] RHV-M Deployment/Install Needs it's own UUID
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	JW <justin>
Component:	ovirt-engine	Assignee:	Ori Liel <oliel>
Status:	CLOSED ERRATA	QA Contact:	Guilherme Santos <gdeolive>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4.0	CC:	lsvaty, michal.skrivanek, mperina, mtessun, pchavva
Target Milestone:	ovirt-4.4.3	Keywords:	FutureFeature, Reopened, ZStream
Target Release:	---
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.3.8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-24 13:09:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1691340, 1825231

Description JW 2020-04-16 20:54:04 UTC

Description of problem:

For data protection, the RHV-M is registered using the DNS name or IP for RHV-M along with the credentials which are used with the REST API calls. Because a RHV-M may have more then one DNS name potentially, one or more IPs, the same RHV-M can potentially be registered within the data protection system more then once as there is no way to verify uniqueness of the RHV-M.

Almost everything within RHV-M has a unique ID/UUID, however there seems to be no UUID specific to just the Deployment/Install of RHV-M that can be used/keyed off to ensure uniqueness and prevent RHV-M from being registered more then once using different DNS names or IPs addresses.

The ask is to provide a UUID via REST API for the Deployment/Install that will be unique for each Deployment/Install of RHV-M.

The UUID should be accessible via the REST API calls e.g. /ovirt-engine/api

Perhaps added within the <product_info></product_info> or somewhere else, does not matter to much as long as the UUID can be found via REST API call. 


How reproducible:

100% reproducible


Steps to Reproduce:
1. No indication in the API documentation for how to get a UUID for a RHV-M.
2.
3.

Comment 1 Michal Skrivanek 2020-04-17 06:30:21 UTC

does this need to be a private bug? You would still see it when public...

Comment 2 RHEL Program Management 2020-04-17 06:30:29 UTC

The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 3 Pavan Chavva 2020-04-17 12:19:39 UTC

(In reply to Michal Skrivanek from comment #1)

> does this need to be a private bug? You would still see it when public...

I am making it private,thanks for noticing.

Best,
Pavan.

Comment 4 Michal Skrivanek 2020-06-03 07:33:56 UTC

ah, sorry, I meant it the other way around. There's no customer details anywhere so I was suggesting to make it a simple public bug

Comment 5 Ori Liel 2020-10-05 11:17:28 UTC

patch submitted for ovirt-engine-api-model

  https://gerrit.ovirt.org/#/c/111481/

another patch will soon follow for ovirt-engine

Comment 10 Guilherme Santos 2020-10-26 16:34:47 UTC

Verified on:
ovirt-engine-4.4.3.8-0.1.el8ev.noarch

Steps:
1. curl -k -u admin@internal:<psswd> https://<engine-fqdn>/ovirt-engine/api/ | grep '<product_info' -A 10
    <product_info>
        <instance_id>1a787f22-17a4-11eb-98e1-001a4a013f1f</instance_id>
        <name>Red Hat Virtualization Manager</name>
        <version>
            <build>3</build>
            <full_version>4.4.3.8-0.1.el8ev</full_version>
            <major>4</major>
            <minor>4</minor>
            <revision>0</revision>
        </version>
    </product_info>

Results:
UID of RHV-M deployment <instance_id> present on API on product_info

Comment 15 errata-xmlrpc 2020-11-24 13:09:21 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Low: Red Hat Virtualization security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHSA-2020:5179