Hide Forgot
Description of problem: Virt-who can't get connect rhevm4.0 api url result in virt-who failed to get h/g mapping info when monitor rhevm4.0. Version-Release number of selected component (if applicable): rhevm-4.0.0.4-0.1.el7ev.noarch rhev-hypervisor7-ng-4.0-20160609.0 virt-who-0.14-9.el7.noarch How reproducible: Always Steps to Reproduce: 1. On rhevm4.0 webUI, add rhev-hypervisor7-ng-4.0-20160609.0 to rhevm-4.0.0.4-0.1.el7ev.noarch. 2. Register rhevh to satellite6.2 3. Configure virt-who run at rhevm mode and restart virt-who service [root@bootp-73-5-249 ~]# cat /etc/sysconfig/virt-who | grep -v ^# | grep -v ^$ VIRTWHO_DEBUG=1 VIRTWHO_RHEVM=1 VIRTWHO_RHEVM_OWNER=ACME_Corporation VIRTWHO_RHEVM_ENV=Library VIRTWHO_RHEVM_SERVER=https://hp-z220-04.qe.lab.eng.nay.redhat.com:443/ovirt-engine/ VIRTWHO_RHEVM_USERNAME=admin@internal VIRTWHO_RHEVM_PASSWORD=redhat [root@bootp-73-5-249 ~]# service virt-who restart && tail -f /var/log/rhsm/rhsm.log 2016-06-14 02:36:55,177 [INFO] @virt.py:317 - Waiting 3600 seconds before retrying backend 'env/cmdline' 2016-06-14 02:49:31,858 [INFO] @virtwho.py:697 - Using configuration "env/cmdline" ("rhevm" mode) 2016-06-14 02:49:31,859 [DEBUG] @virtwho.py:216 - Starting infinite loop with 3600 seconds interval 2016-06-14 02:49:31,954 [ERROR] @virt.py:306 - Virt backend 'env/cmdline' fails with exception: Traceback (most recent call last): File "/usr/share/virt-who/virt/virt.py", line 301, in run self._run() File "/usr/share/virt-who/virt/virt.py", line 332, in _run report = self._get_report() File "/usr/share/virt-who/virt/virt.py", line 274, in _get_report return HostGuestAssociationReport(self.config, self.getHostGuestMapping()) File "/usr/share/virt-who/virt/rhevm/rhevm.py", line 104, in getHostGuestMapping clusters_xml = ElementTree.parse(self.get(self.clusters_url)) File "/usr/share/virt-who/virt/rhevm/rhevm.py", line 89, in get return urllib2.urlopen(request) File "/usr/lib64/python2.7/urllib2.py", line 154, in urlopen return opener.open(url, data, timeout) File "/usr/lib64/python2.7/urllib2.py", line 437, in open response = meth(req, response) File "/usr/lib64/python2.7/urllib2.py", line 550, in http_response 'http', request, response, code, msg, hdrs) File "/usr/lib64/python2.7/urllib2.py", line 475, in error return self._call_chain(*args) File "/usr/lib64/python2.7/urllib2.py", line 409, in _call_chain result = func(*args) File "/usr/lib64/python2.7/urllib2.py", line 558, in http_error_default raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) HTTPError: HTTP Error 404: Not Found 2016-06-14 02:49:31,956 [INFO] @virt.py:317 - Waiting 3600 seconds before retrying backend 'env/cmdline' Actual results: Virt-who failed to get host/guest mapping info. Expected results: Virt-who should get host/guest mapping info successfully. Additional info:
This bug is fixed upstream and for 7.3. If we need to stay on RHEL-7.2 for RHEVM-4.0, we have to fix this in the z-stream.
hi radek, is approved or not about the 7.2 z-stream?
We need either GSSApproved or PMApproved keyword in order to fix in the z-stream. Moran, can we please get 7.2.z? flag and PMApproved for this bug? We believe that this should be fixed for RHEV-4.0.
(In reply to Radek Novacek from comment #4) > We need either GSSApproved or PMApproved keyword in order to fix in the > z-stream. > > Moran, can we please get 7.2.z? flag and PMApproved for this bug? We believe > that this should be fixed for RHEV-4.0. I have added the 7.2.z flag, though PM approval should come from Scott on that scope.
Moran, it seems that you accidentally added rhel-7.2.0 instead of rhel-7.2.z flag. Scott, can you please approve this bug for rhel-7.2.z?
Ping, can we please get this bug approved for 7.2.z? This bug prevents all users from using virt-who with RHEVM-4.0.
I was under the impression that virt-who is not even used for RHEV.... It is only used for RHEL using the VDC SKU in a VMware environment?
(In reply to Scott Herold from comment #10) > I was under the impression that virt-who is not even used for RHEV.... It is > only used for RHEL using the VDC SKU in a VMware environment? Apparently being used by Satellite, some reference can be found here: https://access.redhat.com/solutions/1328783 RHEVM exists as supported platform on documentation as well: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/sect-Red_Hat_Satellite-Installation_Guide-Managing_Hypervisors_and_Virtual_Guest_Subscriptions-Supported_Hypervisors.html
AFAIK it is also used on RHEV-H for some entitlement reason
And this bug is also blocking virt-who testing on RHVH
Requesting an 7.3 exception and a 7.2.z backport as it affects RHVH
waiting for the rhel7.2.z approved, change the status to NEW ...
Tom, can you provide 7.2.z - it's needed in RHEV.
Eko, this bug is for 7.3, where this bug is fixed. For 7.2.z, new bug will be cloned from this one. Switching the status back to ON_QA.
rhel-7.4.0? removed.
verified with virt-who-0.14-9.el7_2.3 for rhel7.2
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://rhn.redhat.com/errata/RHBA-2016-2387.html