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 add vm to esx host on the vcenter, it will pop up error message including "Cannot read VM list from ESX" and RestlibException
Version-Release number of selected component (if applicable):
subscription-manager-1.12.10-1.el6.x86_64
python-rhsm-1.12.5-1.el6.x86_64
virt-who-0.10-4.el6.noarch
katello-headpin-1.4.3.26-1.el6sam_splice.noarch
candlepin-0.9.6.4-1.el6sam.noarch
How reproducible:
Always
Steps to Reproduce:
1. Prepare RHEL6.6 with latest subscription-manager and virt-who installed.
ESX host has been added to vcenter, And ESX host has three guest.
My test env as the following:
vCenter: 10.66.79.51
ESX host 1: 10.66.128.160
2. Configure virt-who in ESX mode as the following:
[root@hp-z220-03 ~]# cat /etc/sysconfig/virt-who
VIRTWHO_BACKGROUND=1
# Enable debugging output.
VIRTWHO_DEBUG=1
VIRTWHO_INTERVAL=5
# Register ESX machines using vCenter
VIRTWHO_ESX=1
# Option for ESX mode
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.Start virt-who service
[root@hp-z220-03 ~]# service virt-who start
[root@hp-z220-03 ~]# service virt-who status
virt-who (pid 15975) is running...
4. Register the RHEL6.6 to SAM server
# Subscription-manager register --username=admin --password=admin
5. Monitor the rhsm log :
# tail -f /var/log/rhsm/rhsm.log
6. Bring up vclient which connect to vcenter, add a vm to esx host. Then check virt-who log
Actual results:
It will show "Cannot read VM list from ESX for host aee4ff00-8c33-11e2-994a-6c3be51d959a (len(obj) <= 1) "
2014-08-04 11:05:01,270 [INFO] @subscriptionmanager.py:116 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [564d0676-800c-ea35-b2f6-982fa056ae84], 44454c4c-4200-1034-8039-b8c04f503258: []}
2014-08-04 11:05:14,784 [ERROR] @esx.py:246 - Cannot read VM list from ESX for host aee4ff00-8c33-11e2-994a-6c3be51d959a (len(obj) <= 1)
2014-08-04 11:05:15,093 [ERROR] @esx.py:246 - Cannot read VM list from ESX for host aee4ff00-8c33-11e2-994a-6c3be51d959a (len(obj) <= 1)
2014-08-04 11:05:15,095 [INFO] @subscriptionmanager.py:116 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [564d0676-800c-ea35-b2f6-982fa056ae84], 44454c4c-4200-1034-8039-b8c04f503258: []}
2014-08-04 11:05:27,450 [INFO] @subscriptionmanager.py:116 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [423a7a70-0b36-406f-27c9-518ccc4e42b6, 564d0676-800c-ea35-b2f6-982fa056ae84], 44454c4c-4200-1034-8039-b8c04f503258: []}
Expected results:
It shouldn't show this kind of error message
Additional info:
I'm afraid not. because it appears this problem when there is a guest on given host. please see the log as the following.
Meanwhile, I think it still needn't show this error message in the virt-who log if it's correct to appear this error when there is no guest on given host.
2014-08-04 11:05:01,270 [INFO] @subscriptionmanager.py:116 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [564d0676-800c-ea35-b2f6-982fa056ae84], 44454c4c-4200-1034-8039-b8c04f503258: []}
2014-08-04 11:05:14,784 [ERROR] @esx.py:246 - Cannot read VM list from ESX for host aee4ff00-8c33-11e2-994a-6c3be51d959a (len(obj) <= 1)
2014-08-04 11:05:15,093 [ERROR] @esx.py:246 - Cannot read VM list from ESX for host aee4ff00-8c33-11e2-994a-6c3be51d959a (len(obj) <= 1)
2014-08-04 11:05:15,095 [INFO] @subscriptionmanager.py:116 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [564d0676-800c-ea35-b2f6-982fa056ae84], 44454c4c-4200-1034-8039-b8c04f503258: []}
2014-08-04 11:05:27,450 [INFO] @subscriptionmanager.py:116 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [423a7a70-0b36-406f-27c9-518ccc4e42b6, 564d0676-800c-ea35-b2f6-982fa056ae84], 44454c4c-4200-1034-8039-b8c04f503258: []}
(In reply to Radek Novacek from comment #2)
> Do I understand it correctly that the error only appears when there is no
> guest on given host?
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.
http://rhn.redhat.com/errata/RHBA-2014-1513.html
Description of problem: When add vm to esx host on the vcenter, it will pop up error message including "Cannot read VM list from ESX" and RestlibException Version-Release number of selected component (if applicable): subscription-manager-1.12.10-1.el6.x86_64 python-rhsm-1.12.5-1.el6.x86_64 virt-who-0.10-4.el6.noarch katello-headpin-1.4.3.26-1.el6sam_splice.noarch candlepin-0.9.6.4-1.el6sam.noarch How reproducible: Always Steps to Reproduce: 1. Prepare RHEL6.6 with latest subscription-manager and virt-who installed. ESX host has been added to vcenter, And ESX host has three guest. My test env as the following: vCenter: 10.66.79.51 ESX host 1: 10.66.128.160 2. Configure virt-who in ESX mode as the following: [root@hp-z220-03 ~]# cat /etc/sysconfig/virt-who VIRTWHO_BACKGROUND=1 # Enable debugging output. VIRTWHO_DEBUG=1 VIRTWHO_INTERVAL=5 # Register ESX machines using vCenter VIRTWHO_ESX=1 # Option for ESX mode 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.Start virt-who service [root@hp-z220-03 ~]# service virt-who start [root@hp-z220-03 ~]# service virt-who status virt-who (pid 15975) is running... 4. Register the RHEL6.6 to SAM server # Subscription-manager register --username=admin --password=admin 5. Monitor the rhsm log : # tail -f /var/log/rhsm/rhsm.log 6. Bring up vclient which connect to vcenter, add a vm to esx host. Then check virt-who log Actual results: It will show "Cannot read VM list from ESX for host aee4ff00-8c33-11e2-994a-6c3be51d959a (len(obj) <= 1) " 2014-08-04 11:05:01,270 [INFO] @subscriptionmanager.py:116 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [564d0676-800c-ea35-b2f6-982fa056ae84], 44454c4c-4200-1034-8039-b8c04f503258: []} 2014-08-04 11:05:14,784 [ERROR] @esx.py:246 - Cannot read VM list from ESX for host aee4ff00-8c33-11e2-994a-6c3be51d959a (len(obj) <= 1) 2014-08-04 11:05:15,093 [ERROR] @esx.py:246 - Cannot read VM list from ESX for host aee4ff00-8c33-11e2-994a-6c3be51d959a (len(obj) <= 1) 2014-08-04 11:05:15,095 [INFO] @subscriptionmanager.py:116 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [564d0676-800c-ea35-b2f6-982fa056ae84], 44454c4c-4200-1034-8039-b8c04f503258: []} 2014-08-04 11:05:27,450 [INFO] @subscriptionmanager.py:116 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [423a7a70-0b36-406f-27c9-518ccc4e42b6, 564d0676-800c-ea35-b2f6-982fa056ae84], 44454c4c-4200-1034-8039-b8c04f503258: []} Expected results: It shouldn't show this kind of error message Additional info: