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.
Bug 1231602 - virt-who can't connect to vcenter instantly after reboot vcenter
Summary: virt-who can't connect to vcenter instantly after reboot vcenter
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-who
Version: 6.7
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Radek Novacek
QA Contact: gaoshang
URL:
Whiteboard:
Depends On:
Blocks: 1247866
TreeView+ depends on / blocked
 
Reported: 2015-06-15 03:20 UTC by Liushihui
Modified: 2016-12-01 00:35 UTC (History)
4 users (show)

Fixed In Version: virt-who-0.16-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1247866 (view as bug list)
Environment:
Last Closed: 2016-05-10 23:55:44 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:0859 0 normal SHIPPED_LIVE virt-who bug fix and enhancement update 2016-05-10 22:44:47 UTC

Description Liushihui 2015-06-15 03:20:47 UTC 
Description of problem:
Although vcenter reboot successfully, virt-who can't connect to vcenter immediately, it take 30min to re-connect to vcenter

Version-Release number of selected component (if applicable):
subscription-manager-1.14.10-1.el6.x86_64
python-rhsm-1.14.3-1.el6.x86_64
virt-who-0.12-10.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. virt-who connect to vcenter successfully, it can report host/guest associate every 5s
2. Reboot vcenter, make sure vclient can connect vcenter successfully
3. Check the virt-who's log.

Actual results:
virt-who can't connect to vcenter until 30 min later.
2015-06-11 17:58:41,593 [INFO]  @subscriptionmanager.py:124 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [4227d611-0abc-fc5e-7538-07ebd83fa9ba, 564dab7d-3b72-51a1-eeda-586036106892, 4224a77f-1c50-42cb-3507-2b68b447ed60, 42276a15-3931-a114-1e69-b1c060c8af3d, 422707cc-a2e3-3e85-0fa9-5d93ff009f16]}
2015-06-11 17:58:41,593 [DEBUG]  @subscriptionmanager.py:76 - Authenticating with certificate: /etc/pki/consumer/cert.pem
2015-06-11 17:58:41,861 [INFO]  @virtwho.py:147 - virt-who host/guest association update successful
2015-06-11 17:58:46,936 [DEBUG]  @esx.py:135 - Waiting for ESX changes
2015-06-11 17:58:46,937 [INFO]  @subscriptionmanager.py:124 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [4227d611-0abc-fc5e-7538-07ebd83fa9ba, 564dab7d-3b72-51a1-eeda-586036106892, 4224a77f-1c50-42cb-3507-2b68b447ed60, 42276a15-3931-a114-1e69-b1c060c8af3d, 422707cc-a2e3-3e85-0fa9-5d93ff009f16]}
2015-06-11 17:58:46,937 [DEBUG]  @subscriptionmanager.py:76 - Authenticating with certificate: /etc/pki/consumer/cert.pem
2015-06-11 17:58:47,201 [INFO]  @virtwho.py:147 - virt-who host/guest association update successful
===========After 30min , virt-who connect to vcenter===========
2015-06-11 18:28:47,050 [DEBUG]  @esx.py:98 - Wait for ESX event finished, timeout
2015-06-11 18:28:47,749 [DEBUG]  @esx.py:53 - Log into ESX
2015-06-11 18:28:48,807 [DEBUG]  @esx.py:56 - Creating ESX event filter
2015-06-11 18:28:49,152 [INFO]  @subscriptionmanager.py:124 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [422707cc-a2e3-3e85-0fa9-5d93ff009f16, 4224a77f-1c50-42cb-3507-2b68b447ed60, 4227d611-0abc-fc5e-7538-07ebd83fa9ba, 564dab7d-3b72-51a1-eeda-586036106892]}


Expected results:
virt-who should report host/guest to server side immediate after reboot vcenter

Additional info:
Comment 3 Radek Novacek 2015-12-15 09:55:48 UTC 
The fix for this issue has been applied upstream: 

https://github.com/virt-who/virt-who/commit/69bfd3aa5c0384ba7da3cc3f8f03a92cbaa2588a

Now virt-who should notice that ESX server is not functional and recover in about one minute.
Comment 4 Radek Novacek 2015-12-17 12:29:44 UTC 
Fixed by rebase to virt-who-0.16-1.el6.
Comment 6 Liushihui 2016-02-23 08:55:09 UTC 
Verified it on virt-who-0.16-4.el6.noarch since virt-who can re-monitor h/g mapping info after reboot vcenter.Therefore, verified it.
Comment 8 errata-xmlrpc 2016-05-10 23:55:44 UTC 
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/RHEA-2016-0859.html
Note You need to log in before you can comment on or make changes to this bug.