Bug 1247866
Summary: | virt-who can't connect to vcenter instantly after reboot vcenter | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Liushihui <shihliu> |
Component: | virt-who | Assignee: | Radek Novacek <rnovacek> |
Status: | CLOSED ERRATA | QA Contact: | Eko <hsun> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.2 | CC: | hsun, ldai, ovasik, owwang, rbalakri, rnovacek, sgao |
Target Milestone: | rc | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | virt-who-0.17-1.el7 | Doc Type: | No Doc Update |
Doc Text: |
undefined
|
Story Points: | --- |
Clone Of: | 1231602 | Environment: | |
Last Closed: | 2016-11-04 05:05:51 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: | |||
Bug Depends On: | 1231602 | ||
Bug Blocks: |
Comment 1
Eko
2015-09-01 08:11:25 UTC
It seems that the error in step 3 is some kind of internal failure in vCenter (some internal service is not yet started after the reboot). I don't think there is much that virt-who can do about it, apart for hiding the error (that would be bad idea because it can hide other problems). It looks like the bug is now fixed. Can we close this report now? Radek, According to the comment 1,this problem has been resolved in the latest virt-who. I think we can close this bug on this version. Therefore, close it as worksforme. Thanks. Checked version: virt-who-0.14-4.el7.noarch subscription-manager-1.15.9-6.el7.x86_64 python-rhsm-1.15.4-2.el7.x86_64 Satellite6.1.0-20150820.0 It has reproduced on virt-who-0.14-7.el7.noarch, Therefore, reopen it. Reproduced version: virt-who-0.14-7.el7.noarch subscription-manager-1.15.9-7.el7.x86_64 python-rhsm-1.15.4-4.el7.x86_64 SAM-1.4.1-RHEL-6-20141113.0 Reproduced process: 1. Register system to SAM 2. Configure virt-who run at esx mode, and the refresh interval is 5s. 3. Restart virt-who service, virt-who send the host/guest mapping to SAM 4. Stop vcenter, then start vcenter, check the virt-who's log Result: virt-who can't connect to vcenter until 30 min later. 2015-09-16 17:13:22,820 [DEBUG] @esx.py:142 - Waiting for ESX changes 2015-09-16 17:13:22,824 [DEBUG] @subscriptionmanager.py:112 - Authenticating with certificate: /etc/pki/consumer/cert.pem 2015-09-16 17:13:22,846 [DEBUG] @subscriptionmanager.py:146 - Checking if server has capability 'hypervisor_async' 2015-09-16 17:13:22,867 [DEBUG] @subscriptionmanager.py:158 - Server does not have 'hypervisors_async' capability 2015-09-16 17:13:22,868 [INFO] @subscriptionmanager.py:165 - Sending update in hosts-to-guests mapping: { "93b45c80-28ec-11e2-87c4-b4b52fe0f08d": [ { "guestId": "422c92cb-14b2-e7a5-77fe-a530c7311de7", "state": 1, "attributes": { "active": 1, "virtWhoType": "esx", "hypervisorType": "vmware" } } ], "826c4f80-28ee-11e2-b149-b4b52fe0ce88": [] } ******************After 30min, virt-who send h/g mapping to SAM again******** 2015-09-16 17:43:22,927 [DEBUG] @esx.py:105 - Wait for ESX event finished, timeout 2015-09-16 17:43:22,968 [DEBUG] @esx.py:55 - Log into ESX 2015-09-16 17:43:23,352 [DEBUG] @esx.py:58 - Creating ESX event filter 2015-09-16 17:43:23,410 [DEBUG] @esx.py:142 - Waiting for ESX changes 2015-09-16 17:43:23,412 [DEBUG] @subscriptionmanager.py:112 - Authenticating with certificate: /etc/pki/consumer/cert.pem 2015-09-16 17:43:23,443 [DEBUG] @subscriptionmanager.py:146 - Checking if server has capability 'hypervisor_async' 2015-09-16 17:43:23,473 [DEBUG] @subscriptionmanager.py:158 - Server does not have 'hypervisors_async' capability 2015-09-16 17:43:23,473 [INFO] @subscriptionmanager.py:165 - Sending update in hosts-to-guests mapping: { "93b45c80-28ec-11e2-87c4-b4b52fe0f08d": [ { "guestId": "422c92cb-14b2-e7a5-77fe-a530c7311de7", "state": 1, "attributes": { "active": 1, "virtWhoType": "esx", "hypervisorType": "vmware" } } ], "826c4f80-28ee-11e2-b149-b4b52fe0ce88": [] } Expected result: virt-who should report host/guest to SAM immediate after reboot vcenter This bug seems to be similar to bug 1247866. Moving to RHEL-7.3. Since this bug is cloned from bug #1231602 that is already fixed in RHEL-6.8 and the code base for 7.3 rebase is the same, the upcoming rebase of virt-who should fix this issue. Fixed in virt-who-0.17-1.el7. Verified it on virt-who-0.17-2.el7.noarch since virt-who can connect vcenter every refresh interval, virt-who also can send h/g mapping info to server immediately after reboot vcenter successfully. 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 |