Bug 2001551 - Allow more granular checks with rhv-image-discrepancies
Summary: Allow more granular checks with rhv-image-discrepancies
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhv-log-collector-analyzer
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.4.9
: 4.4.9
Assignee: Germano Veit Michel
QA Contact: Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-06 11:25 UTC by Roman Hodain
Modified: 2021-11-16 14:47 UTC (History)
2 users (show)

Fixed In Version: rhv-log-collector-analyzer-1.0.11-1.el8ev
Doc Type: Enhancement
Doc Text:
In this release, rhv-image-discrepancies now allows more granular checks. Two new options have been added to rhv-image-discrepancies command line to restrict the run to specific data centers or storage domains. If both are specified it is restricted to the intersection of both. -p --pool-uuid: limit run to data centers, can be specified multiple times -s --storage-uuid: limit run to storage domains, can be specified multiple times For example: # rhv-image-discrepancies -p=5bbe9966-ea58-475f-863f -s=977ba581-23e5-460a-b1de
Clone Of:
Environment:
Last Closed: 2021-11-16 14:46:57 UTC
oVirt Team: Integration
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-43382 0 None None None 2021-09-06 11:26:04 UTC
Red Hat Product Errata RHSA-2021:4626 0 None None None 2021-11-16 14:47:07 UTC

Comment 1 Roman Hodain 2021-09-06 11:27:03 UTC 
Add parameters for DC and SD and limit the test to specific DC if no SD is specified or run the test only on one SD if SD is specified.
Comment 2 Germano Veit Michel 2021-09-10 04:11:58 UTC 
Hi Roman, do you think its ok to specify DC/SD by UUID or we need to use names or even allow both?
Does the customer requesting this know the UUIDs or how to get them?

Thanks for raising this, makes a lot of sense on big envs.
Comment 3 Roman Hodain 2021-09-21 07:42:15 UTC 
Hi, it is ok to provide just UUIDs as they can be found in the WebAdmin
Comment 6 Tamir 2021-09-30 16:02:13 UTC 
Verified on RHV 4.4.9-2. All looks good to me.

Env:
  - Engine instance with RHV 4.4.9-2 and RHEL 8.5 installed, rhv-log-collector-analyzer-1.0.11-1.el8ev.
  - 3 Hosts with RHV 4.4.9-2 and RHEL 8.5, vdsm-4.40.90.1-1.el8ev, ovirt-engine-4.4.9-0.6.el8ev

Steps:

In Admin Portal:

1. Create 2 4.6 data centers and a 4.6 cluster for each.
2. Install 2 hosts related to one of those clusters and 1 host to the other. Add a storage domain for each cluster.
3. Run the attached test commands and compare results.


Results (As Expected):
1. 2 4.6 data centers and 2 4.6 clusters were created.
2. The hosts were installed correctly, the storage domains were created.
3. The tests passed (the results are attached)
Comment 11 errata-xmlrpc 2021-11-16 14:46:57 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 (Moderate: RHV Manager (ovirt-engine) security update [ovirt-4.4.9]), 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-2021:4626
Note You need to log in before you can comment on or make changes to this bug.