RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1346160 - [RHEVH7-ng-4.0]Virt-who failed to connect rhevm4.0 as "HTTP Error 404"
Summary: [RHEVH7-ng-4.0]Virt-who failed to connect rhevm4.0 as "HTTP Error 404"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who
Version: 7.2
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: rc
: ---
Assignee: Radek Novacek
QA Contact: Eko
URL:
Whiteboard:
Depends On:
Blocks: ovirt-node-ng-platform 1372187 1372563
TreeView+ depends on / blocked
 
Reported: 2016-06-14 06:52 UTC by Liushihui
Modified: 2019-12-16 05:56 UTC (History)
15 users (show)

Fixed In Version: virt-who-0.17-3.el7
Doc Type: Bug Fix
Doc Text:
Prior to this update, virt-who failed to connect to Red Hat Enterprise Virtualization Manager 4.0, as virt-who did not properly parse the virt-who configuration file. With this update, virt-who reads its configuration as expected, and can successfully connect to Red Hat Enterprise Virtualization Manager 4.0.
Clone Of:
: 1372187 1372563 (view as bug list)
Environment:
Last Closed: 2016-11-04 05:09:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2387 0 normal SHIPPED_LIVE virt-who bug fix and enhancement update 2016-11-03 13:53:39 UTC

Description Liushihui 2016-06-14 06:52:05 UTC
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:

Comment 2 Radek Novacek 2016-06-15 08:49:13 UTC
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.

Comment 3 Eko 2016-06-23 07:33:57 UTC
hi radek,
is approved or not about the 7.2 z-stream?

Comment 4 Radek Novacek 2016-06-23 08:10:08 UTC
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.

Comment 6 Moran Goldboim 2016-06-26 13:26:33 UTC
(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.

Comment 8 Radek Novacek 2016-06-30 11:46:55 UTC
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?

Comment 9 Radek Novacek 2016-07-13 08:26:29 UTC
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.

Comment 10 Scott Herold 2016-07-15 19:37:41 UTC
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?

Comment 11 Moran Goldboim 2016-07-19 09:03:24 UTC
(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

Comment 12 Fabian Deutsch 2016-08-22 09:59:15 UTC
AFAIK it is also used on RHEV-H for some entitlement reason

Comment 13 Fabian Deutsch 2016-08-22 09:59:42 UTC
And this bug is also blocking virt-who testing on RHVH

Comment 14 Fabian Deutsch 2016-08-22 10:00:29 UTC
Requesting an 7.3 exception and a 7.2.z backport as it affects RHVH

Comment 15 Eko 2016-08-24 03:12:11 UTC
waiting for the rhel7.2.z approved, change the status to NEW ...

Comment 16 Fabian Deutsch 2016-08-24 06:01:34 UTC
Tom, can you provide 7.2.z - it's needed in RHEV.

Comment 17 Radek Novacek 2016-08-24 08:06:46 UTC
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.

Comment 19 Radek Novacek 2016-08-25 05:38:03 UTC
rhel-7.4.0? removed.

Comment 22 Eko 2016-09-09 02:16:11 UTC
verified with virt-who-0.14-9.el7_2.3 for rhel7.2

Comment 25 errata-xmlrpc 2016-11-04 05:09:22 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://rhn.redhat.com/errata/RHBA-2016-2387.html


Note You need to log in before you can comment on or make changes to this bug.