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.
Since it also exist on virt-who-0.16-5.el6.noarch, therefore, track it on RHEL6.8.
+++ This bug was initially created as a clone of Bug #1265582 +++
Description of problem:
When virt-who connect to vcenter through proxy, virt-who will generate too many info of "Wait for ESX event finished, timeout"
Version-Release number of selected component (if applicable):
virt-who-0.14-8.el7.noarch
subscription-manager-1.15.9-10.el7.x86_64
python-rhsm-1.15.4-5.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Register system to SAM
2. Configure virt-who run at esx mode and make virt-who connect vcenter through proxy. then restart virt-who service.
3. Restart squid on proxy
[root@samdns ~]# service squid restart
4. Before squid is restarted, check the virt-who's log
Actual results:
It will generate over 100 times "Wait for ESX event finished, timeout" info every one minute.
2015-09-23 17:13:56,001 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,005 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,008 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,011 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,015 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,019 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,022 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,025 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,029 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,032 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,036 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,039 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,042 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,046 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,049 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,052 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,056 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
2015-09-23 17:13:56,059 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout
............
Expected results:
Virt-who shouldn't generate too many redundant timeout info in the log.
Additional info:
After squid is restarted ,virt-who can resend h/g mapping to server
I'm not able to reproduce it, when I restart squid service, virt-who retries the connection after 60 seconds:
2016-03-10 10:49:29,504 ERROR: Virt backend 'esx' fails with exception:
URLError: <urlopen error [Errno 111] Connection refused>
2016-03-10 10:49:29,505 INFO: Waiting 60 seconds before retrying backend 'esx'
2016-03-10 10:50:29,965 INFO: Report for config "esx" haven't changed, not sending
It seems that your squid doesn't close the connection when being restarted and therefore virt-who gets some other error that it doesn't handle properly.
Can you provide me an environment where I can reproduce it?