Description of problem: I would be nice to have Data Center and Storage Domain name in the rhv-image-discrepancies output report. This way end user will need which DC and SD disk images are flagged in the report. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
[root@rhvm ~]# ./rhv-image-discrepancies IT IS HIGHLY RECOMMENDED YOU RUN THIS WITH RED HAT SUPPORT INVOLVED Do you want to continue? [y/N] y Using host rhvh-1.toca.local on DC 3e956788-433d-11ec-8a5d-5254006fd7c7 to run dump-volume-chains Running vdsm-tool dump-volume-chains 088f1101-8024-4e62-8818-e32f8b044177... Running vdsm-tool dump-volume-chains 2f93a595-a602-4bfc-b35e-9e78b89f27b4... Checking storage domain 'hosted_storage' (088f1101-8024-4e62-8818-e32f8b044177) from data-center 'Default' No problems found Checking storage domain 'Synology' (2f93a595-a602-4bfc-b35e-9e78b89f27b4) from data-center 'Default' Image 945148ea-16a0-440e-aa23-a82a39e0e928 is not legal in the storage Total problems found: 1 [root@rhvm ~]#
Verified on rhv-log-collector-analyzer-1.0.13-1.el8ev.noarch Datacenter and storage domain information shown on rhv-image-discrepancies output
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) [ovirt-4.5.0] security 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-2022:4711