Red Hat Bugzilla – Bug 1271085
virt-who shows "Communication with server failed" with RateLimitExceededException
Last modified: 2016-11-30 19:36:01 EST
Description of problem:
when migrated a guest to another host, virt-who will show RateLimitExceededException and can't send the mapping info to stage candlepin.
Version-Release number of selected component (if applicable):
- RHEL7.2-20151008.0-Server-x86_64 + vdsm mode against Stage candlepin
Steps to Reproduce:
1. prepare two hosts with vdsm mode
2. prepare a guest on host1
2. register the two hosts and guest to stage candlepin
3. subscribe a unlimit pool for the two hosts
4. subscribe the bonus pool for the guest
5. migrate the guest to host2
6. check the rhsm.log on host2, following error message will be found:
2015-10-13 15:08:10,196 [INFO] @subscriptionmanager.py:136 - Sending domain info: [
2015-10-13 15:08:13,497 [ERROR] @virtwho.py:190 - Error in communication with subscription manager:
Traceback (most recent call last):
File "/usr/share/virt-who/virtwho.py", line 171, in send
File "/usr/share/virt-who/virtwho.py", line 196, in _sendGuestList
File "/usr/share/virt-who/manager/subscriptionmanager/subscriptionmanager.py", line 139, in sendVirtGuests
File "/usr/lib64/python2.7/site-packages/rhsm/connection.py", line 947, in updateConsumer
ret = self.conn.request_put(method, params)
File "/usr/lib64/python2.7/site-packages/rhsm/connection.py", line 653, in request_put
return self._request("PUT", method, params)
File "/usr/lib64/python2.7/site-packages/rhsm/connection.py", line 564, in _request
self.validateResponse(result, request_type, handler)
File "/usr/lib64/python2.7/site-packages/rhsm/connection.py", line 627, in validateResponse
RateLimitExceededException will be found, and can't send the mapping info to stage candlepin
no error message found, the mapping info can be sent to stage candlepin normally.
Chris, this will be fixed by your recent changes in the interval reporting, right?
Yes, this will be fixed by my recent changes in the interval reporting.
I think that this error shouldn't appear when the reporting interval is set to some high value.
What VIRTWHO_INTERVAL did you used for testing? Can you retry it with some bigger values (60, 3600, etc.)?
Chris, do you know when is this RateLimitExceeded exception raised? What are the circumstances?
with different interval time (3s, 5s, 15s, 30s, 60s), this exception still can be raised.
As our meeting discussed, if we can't fixed this issue on rhel7.2, we should add it to the release note as a known issue.
Hi Chris & Radek,
I have changed the interval time to 600s, the exception is not found, but 10 minutes is very long for fetching the mapping info when adding or delete a guest. I still suggest to add this issue to release note, do you agree?
Chris, only thing we can do is to release a z-stream fix, but that would mean to backport the RateLimitExceeded exception handling to virt-who-0.14.
Fixed in virt-who-0.17-1.el7.
Verified it on virt-who-0.17-2.el7.noarch since virt-who's minimum refresh interval has updated to 60s, it hasn't shown RateLimitExceededException when add/delete/migrate vm or add/delete host on vcenter. Therefore, verify 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.