Bug 1135408
| Summary: | Can't display the running mode in the virt-who log | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Liushihui <shihliu> | |
| Component: | virt-who | Assignee: | Radek Novacek <rnovacek> | |
| Status: | CLOSED ERRATA | QA Contact: | gaoshang <sgao> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 6.6 | CC: | liliu, ovasik, rbalakri, sgao | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | All | |||
| Whiteboard: | ||||
| Fixed In Version: | virt-who-0.12-1.el6 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1158803 (view as bug list) | Environment: | ||
| Last Closed: | 2015-07-22 07:15:12 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: | ||||
| Bug Blocks: | 1158803 | |||
It's too late for RHEL-6.6, moving to 6.7. Fixed upstream, it will be fixed by rebasing virt-who in RHEL-6.7. Fixed by rebase to virt-who-0.12-1.el6. Verified it on virt-who-0.12-2.el6.noarch.
Do as the bug's description, the running mode can show on the virt-who's log.please see as the following:
2015-04-01 22:32:50,710 [INFO] @virtwho.py:475 - Using configuration "env/cmdline" ("esx" mode)
2015-04-01 22:32:50,710 [DEBUG] @virtwho.py:131 - Starting infinite loop with 10 seconds interval
2015-04-01 22:32:50,802 [DEBUG] @esx.py:51 - Log into ESX
2015-04-01 22:32:51,834 [DEBUG] @esx.py:54 - Creating ESX event filter
2015-04-01 22:32:52,122 [DEBUG] @esx.py:113 - Waiting for ESX changes
2015-04-01 22:32:52,138 [INFO] @subscriptionmanager.py:124 - Sending update in hosts-to-guests mapping: {564d20f4-71b7-acdb-f875-d64ecec4a6c0: [4226082e-2746-17dc-6f01-dc91c6fc7fbb, 4224d6d4-b9ef-cd33-8f19-56bcfc179ed5]}
2015-04-01 22:32:52,139 [DEBUG] @subscriptionmanager.py:76 - Authenticating with certificate: /etc/pki/consumer/cert.pem
2015-04-01 22:32:53,753 [INFO] @virtwho.py:127 - Created host: 54ec3b96-17d6-4c66-ba0d-8bf049dec86a with guests: [4226082e-2746-17dc-6f01-dc91c6fc7fbb, 4224d6d4-b9ef-cd33-8f19-56bcfc179ed5]
2015-04-01 22:33:02,150 [DEBUG] @esx.py:84 - Wait for ESX event finished, timeout
2015-04-01 22:33:02,703 [INFO] @subscriptionmanager.py:124 - Sending update in hosts-to-guests mapping: {564d20f4-71b7-acdb-f875-d64ecec4a6c0: [4226082e-2746-17dc-6f01-dc91c6fc7fbb, 4224d6d4-b9ef-cd33-8f19-56bcfc179ed5]}
2015-04-01 22:33:02,704 [DEBUG] @subscriptionmanager.py:76 - Authenticating with certificate: /etc/pki/consumer/cert.pem
2015-04-01 22:33:02,702 [DEBUG] @esx.py:113 - Waiting for ESX changes
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-2015-1377.html |
Description of problem: When virt-who is running in esx/hyperv/vdsm/rhevm/libvirt mode, it can't display the mode type in the /var/log/rhsm/rhsm.log Version-Release number of selected component (if applicable): subscription-manager-1.12.12-1.el6.x86_64 python-rhsm-1.12.5-1.el6.x86_64 virt-who-0.10-6.el6.noarch katello-headpin-1.4.3.26-1.el6sam_splice.noarch candlepin-0.9.6.5-1.el6sam.noarch How reproducible: Always Steps to Reproduce: 1. Register system to SAM server. 2. Configure virt-who run at esx mode VIRTWHO_DEBUG=1 VIRTWHO_BACKGROUND=1 VIRTWHO_INTERVAL=10 VIRTWHO_ESX=1 VIRTWHO_ESX_OWNER=ACME_Corporation VIRTWHO_ESX_ENV=Library VIRTWHO_ESX_SERVER=10.66.79.51 VIRTWHO_ESX_USERNAME=Administrator VIRTWHO_ESX_PASSWORD=qwer1234P! 3. Restart virt-who service 4. Check the virt-who log at /var/log/rhsm/rhsm.log Actual results: It hasn't display the running mode. 2014-08-29 16:35:38,373 [INFO] @virtwho.py:442 - Using virt-who configuration: virt-who 2014-08-29 16:35:38,373 [DEBUG] @virtwho.py:170 - Starting infinite loop with 10 seconds interval 2014-08-29 16:35:49,194 [INFO] @subscriptionmanager.py:116 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [423acff7-e1c9-787a-1c62-994e09fc7eab], 44454c4c-4200-1034-8039-b8c04f503258: [423a172f-49ad-06f8-f02f-9c3df78b0487, 564d15f6-ec87-12de-53b0-8097fccf069f, 423acf68-1829-364e-5bc4-ca4ce3c660a2, 564dfaf3-aa76-01dc-3a46-c543064f7c3f, 564df668-c88f-af3d-bd92-d41b1de8e156, 564d80be-809b-267a-ebe8-14073fcf10d4]} Expected results: It should display the running mode (esx) as the following: "Virt-who is running in esx mode" Additional info: virt-who is running in hyperv/vdsm/rhevm/libvirt mode has the same problem