Bug 1271085
Summary: | virt-who shows "Communication with server failed" with RateLimitExceededException | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Eko <hsun> |
Component: | virt-who | Assignee: | Radek Novacek <rnovacek> |
Status: | CLOSED ERRATA | QA Contact: | Eko <hsun> |
Severity: | high | Docs Contact: | Jiri Herrmann <jherrman> |
Priority: | high | ||
Version: | 7.2 | CC: | csnyder, csulekha, hsun, jherrman, ldai, ovasik, sgao, shihliu |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | virt-who-0.17-1.el7 | Doc Type: | No Doc Update |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 05:06:16 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Eko
2015-10-13 07:13:51 UTC
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? hi Radek, 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. https://rhn.redhat.com/errata/RHBA-2016-2387.html |