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:
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
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