Description of problem:
Config virt-who connect rhevm with proxy, although virt-who can access the rhevm normally with squid proxy, but it failed to send mapping info to SAM server as "no_proxy" configure hasn't taken effect, it will take effect in python-rhsm-1.15.1-1 or newer.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Register system to SAM
2. Configure virt-who connect with rhevm with proxy.
[root@localhost admin]# cat /etc/sysconfig/virt-who | grep -v ^# | grep -v ^$
3. Restart virt-who service and check virt-who's log
[root@localhost admin]# service virt-who restart && tail -f /var/log/rhsm/rhsm.log
2016-03-16 02:04:10,989 [INFO] @virtwho.py:697 - Using configuration "env/cmdline" ("rhevm" mode)
2016-03-16 02:04:10,990 [DEBUG] @virtwho.py:216 - Starting infinite loop with 3600 seconds interval
2016-03-16 02:04:11,419 [DEBUG] @subscriptionmanager.py:112 - Authenticating with certificate: /etc/pki/consumer/cert.pem
2016-03-16 02:04:11,463 [ERROR] @virtwho.py:190 - Error in communication with subscription manager:
Traceback (most recent call last):
File "/usr/share/virt-who/virtwho.py", line 173, in send
File "/usr/share/virt-who/virtwho.py", line 204, in _sendGuestAssociation
File "/usr/share/virt-who/manager/subscriptionmanager/subscriptionmanager.py", line 145, in hypervisorCheckIn
File "/usr/share/virt-who/manager/subscriptionmanager/subscriptionmanager.py", line 120, in _connect
if not self.connection.ping()['result']:
File "/usr/lib64/python2.7/site-packages/rhsm/connection.py", line 705, in ping
File "/usr/lib64/python2.7/site-packages/rhsm/connection.py", line 550, in request_get
return self._request("GET", method)
File "/usr/lib64/python2.7/site-packages/rhsm/connection.py", line 453, in _request
conn.request(request_type, handler, body=body, headers=headers)
File "/usr/lib64/python2.7/httplib.py", line 979, in request
self._send_request(method, url, body, headers)
File "/usr/lib64/python2.7/httplib.py", line 1013, in _send_request
File "/usr/lib64/python2.7/site-packages/rhsm/connection.py", line 198, in endheaders
File "/usr/lib64/python2.7/httplib.py", line 975, in endheaders
File "/usr/lib64/python2.7/httplib.py", line 835, in _send_output
File "/usr/lib64/python2.7/httplib.py", line 797, in send
File "/usr/lib64/python2.7/site-packages/M2Crypto/httpslib.py", line 206, in connect
raise socket.error, "Proxy connection failed: %d" % code
error: Proxy connection failed: 404
Virt-who can access the rhevm normally with squid proxy, but it failed to send mapping info to satellite server and return 404 error
rhevh7.2 should use the python-rhsm-1.15.1-1 or newer. Then Virt-who can connect rhevm successfully through proxy and "no_proxy" configure can take effect.
Please see a similar bug on rhel6.8:
Liushihui, do you know in which channel python-rhsm-1.15.1-1 was released?
I actually see now that an even newer version was released in RHBA-2015:2122 in RHEL 7.
From where is it expected that we retrieve python-rhsm?
From Satellite (where we retrieve it from today) or from some other source?
Fabian, Rhel7.2 released with python-rhsm-1.15.4- 5(https://errata.devel.redhat.com/advisory/20904),we have test this released version and it hasn't this problem. so could you get it from rhel7.2 related channel?
Yes, we can get that package from RHEL.
But what I need to understand: Are there other packages in RHEV-H related to RHN/RHSM.
And where should we get those packages from?
Consider the wrong rhsm pkgs were built into rhev-hypervisor 7.2 for 3.6, Entitlement QE can not start their valid testing on this build.
So I added "TestBlocker" keyword into this bug to get the fix soon. Thanks.
Please verify this bug with the latest RHEV-H 3.6 build, this bug should be fixed.
with following options, virt-who can send the mapping info to satellite6.1.8 normally, verified it.
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.