Bug 1540953

Summary: virt-who on RHEL6 + RHV4.x - not working when pointing to the RHV-M
Product: Red Hat Enterprise Linux 6 Reporter: Waldirio M Pinheiro <wpinheir>
Component: virt-whoAssignee: Jiri Hnidek <jhnidek>
Status: CLOSED ERRATA QA Contact: Eko <hsun>
Severity: high Docs Contact:
Priority: high    
Version: 6.10CC: csnyder, jhnidek, khowell, rbalakri, salmy, toneata, wpinheir, wpoteat, yuefliu
Target Milestone: rcKeywords: EasyFix, Triaged
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-19 05:21:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Waldirio M Pinheiro 2018-02-01 12:04:56 UTC 
Description of problem:
Customer with RHEL6+Virt-who installed works fine on RHV 3.x, after upgrade to RHV-4.x stop.

Version-Release number of selected component (if applicable):
virt-who-0.18-6.el6_9.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install virt-who on rhel6 machine, the latest version available will be virt-who-0.18-6.el6_9.noarch
2. Configure the conf file according our official docs
3. Execute the command virt-who -d -o

Actual results:
Error according below
---
2018-02-01 00:28:24,421 [virtwho.dc_rhv_01 ERROR] RhevM-1(3174):MainThread @virt.py:run:374 - Virt backend 'dc_rhv_01' fails with error: Unable to connect to RHEV-M server: 404 Client Error: Not Found
---

Expected results:
Collect all information from Manager related to the hypervisors and guests
---
...
2018-02-01 00:30:12,049 [virtwho.main INFO] MainProcess(3191):MainThread @subscriptionmanager.py:hypervisorCheckIn:195 - Sending update in hosts-to-guests mapping for config "dc_rhv_01": 2 hypervisors and 0 guests found
...
---

Additional info:
Comment 4 Kevin Howell 2018-02-01 15:38:19 UTC 
Given existence of patches, marking as EasyFix.
Comment 17 errata-xmlrpc 2018-06-19 05:21:42 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, 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/RHBA-2018:1915