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:
We try to create 100 same configure files in /etc/virt-who.d for esx mode performance testing, that means virt-who will create 100 PIDs and fetch the hosts/guests info from vcenter, some of the PIDs will show "ReadTimeout: HTTPSConnectionPool(host='10.73.3.183', port=443): Read timed out. (read timeout=60)"
Version-Release number of selected component (if applicable):
virt-who-0.17-7.el7.noarch
subscription-manager-1.17.10-1.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. create 100 configure files in /etc/virt-who.d for esx mode
2. restart virt-who
3. check the rhsm.log, will find some configure files failed to fetch host/guests info from vcenter:
2016-08-19 01:00:51,780 [virtwho.test-esx_3 ERROR] Esx-3(16009):MainThread @virt.py:run:379 - Virt backend 'test-esx_3' fails with exception:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/virtwho/virt/virt.py", line 372, in run
self._run()
File "/usr/lib/python2.7/site-packages/virtwho/virt/esx/esx.py", line 175, in _run
options=options)
File "/usr/lib/python2.7/site-packages/suds/client.py", line 542, in __call__
return client.invoke(args, kwargs)
File "/usr/lib/python2.7/site-packages/suds/client.py", line 602, in invoke
result = self.send(soapenv)
File "/usr/lib/python2.7/site-packages/suds/client.py", line 641, in send
reply = transport.send(request)
File "/usr/lib/python2.7/site-packages/virtwho/virt/esx/esx.py", line 96, in send
verify=False
File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 507, in post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 464, in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 576, in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python2.7/site-packages/requests/adapters.py", line 433, in send
raise ReadTimeout(e, request=request)
ReadTimeout: HTTPSConnectionPool(host='10.73.3.183', port=443): Read timed out. (read timeout=60)
Actual results:
So many virt-who PIDs fetch the host/guests info at the same time, thus, some pids will failed due to ReadTimeout
Expected results:
All the Pids can works normally
Additional info:
Given that virt-who connects to the same hypervisor 100 times in parallel, it's quite expected that one hypervisor won't be able to handle all the requests.
Please retry with more than one hypervisor. As I see it now, this is not a bug.
Description of problem: We try to create 100 same configure files in /etc/virt-who.d for esx mode performance testing, that means virt-who will create 100 PIDs and fetch the hosts/guests info from vcenter, some of the PIDs will show "ReadTimeout: HTTPSConnectionPool(host='10.73.3.183', port=443): Read timed out. (read timeout=60)" Version-Release number of selected component (if applicable): virt-who-0.17-7.el7.noarch subscription-manager-1.17.10-1.el7.x86_64 How reproducible: always Steps to Reproduce: 1. create 100 configure files in /etc/virt-who.d for esx mode 2. restart virt-who 3. check the rhsm.log, will find some configure files failed to fetch host/guests info from vcenter: 2016-08-19 01:00:51,780 [virtwho.test-esx_3 ERROR] Esx-3(16009):MainThread @virt.py:run:379 - Virt backend 'test-esx_3' fails with exception: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/virtwho/virt/virt.py", line 372, in run self._run() File "/usr/lib/python2.7/site-packages/virtwho/virt/esx/esx.py", line 175, in _run options=options) File "/usr/lib/python2.7/site-packages/suds/client.py", line 542, in __call__ return client.invoke(args, kwargs) File "/usr/lib/python2.7/site-packages/suds/client.py", line 602, in invoke result = self.send(soapenv) File "/usr/lib/python2.7/site-packages/suds/client.py", line 641, in send reply = transport.send(request) File "/usr/lib/python2.7/site-packages/virtwho/virt/esx/esx.py", line 96, in send verify=False File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 507, in post return self.request('POST', url, data=data, json=json, **kwargs) File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 464, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 576, in send r = adapter.send(request, **kwargs) File "/usr/lib/python2.7/site-packages/requests/adapters.py", line 433, in send raise ReadTimeout(e, request=request) ReadTimeout: HTTPSConnectionPool(host='10.73.3.183', port=443): Read timed out. (read timeout=60) Actual results: So many virt-who PIDs fetch the host/guests info at the same time, thus, some pids will failed due to ReadTimeout Expected results: All the Pids can works normally Additional info: