Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
virt-who can't support connecting rhevm and hyperV through proxy, it just support connecting vcenter through proxy
Version-Release number of selected component (if applicable):
virt-who-0.12-8.el6.noarch
subscription-manager-1.14.6-1.el6.x86_64
python-rhsm-1.14.2-1.el6.x86_64
katello-headpin-1.4.3.28-1.el6sam_splice.noarch
candlepin-0.9.6.5-1.el6sam.noarch
How reproducible:
Always
Steps to Reproduce:
1. Configure virt-who run at rhevm mode/hyperv mode, make sure system which installed virt-who can't connect to rhevm/hyperv directly
2. Configure virt-who connect rhevm/hyperv through proxy as the following
# cat /etc/sysconfig/virt-who
http_proxy=http://10.66.129.158:3128
3. Restart virt-who service
Actual results:
virt-who hasn't connected to proxy and throw error log as the following
2015-06-02 17:04:41,184 [ERROR] @virt.py:225 - Virt backend 'env/cmdline' fails with exception:
Traceback (most recent call last):
File "/usr/share/virt-who/virt/virt.py", line 221, in run
self._run()
File "/usr/share/virt-who/virt/virt.py", line 249, in _run
report = self._get_report()
File "/usr/share/virt-who/virt/virt.py", line 195, in _get_report
return HostGuestAssociationReport(self.config, self.getHostGuestMapping())
File "/usr/share/virt-who/virt/rhevm/rhevm.py", line 79, in getHostGuestMapping
hosts_xml = ElementTree.parse(self.get(self.hosts_url))
File "/usr/share/virt-who/virt/rhevm/rhevm.py", line 66, in get
return urllib2.urlopen(request)
File "/usr/lib64/python2.6/urllib2.py", line 126, in urlopen
return _opener.open(url, data, timeout)
File "/usr/lib64/python2.6/urllib2.py", line 391, in open
response = self._open(req, data)
File "/usr/lib64/python2.6/urllib2.py", line 409, in _open
'_open', req)
File "/usr/lib64/python2.6/urllib2.py", line 369, in _call_chain
result = func(*args)
File "/usr/lib64/python2.6/urllib2.py", line 1198, in https_open
return self.do_open(httplib.HTTPSConnection, req)
File "/usr/lib64/python2.6/urllib2.py", line 1165, in do_open
raise URLError(err)
URLError: <urlopen error [Errno 110] Connection timed out>
Expected results:
I suggest virt-who also support http_proxy when connect to rhevm and hyperv
Additional info:
Verified it on virt-who-0.16-7.el6.noarch since virt-who can connect with rhevm and hyperV through proxy.
Verified version:
virt-who-0.16-7.el6.noarch
subscription-manager-1.16.8-4.el6.x86_64
python-rhsm-1.16.6-1.el6.x86_64
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/RHEA-2016-0859.html