Description of problem: When the parameter "VIRTWHO_INTERVAL" is smaller than 3 seconds (2s or 1s), and after adding a new guest via Vclient on an ESX host, there will be error log in /var/log/rhsm/rhsm.log. But there's no such log if the interval is set to be lager than 3 seconds (if it's set to be 3 seconds, it's not 100% reproducible). Version-Release number of selected component (if applicable): subscription-manager-gui-1.0.20-1.el5 subscription-manager-1.0.20-1.el5 subscription-manager-firstboot-1.0.20-1.el5 python-rhsm-1.0.9-1.el5 virt-who-0.7-8.el5 How reproducible: 100% Steps to Reproduce: 1. configure the virt-who with the following parameters and restart service virt-who: VIRTWHO_BACKGROUND=1 VIRTWHO_DEBUG=1 VIRTWHO_INTERVAL=2 VIRTWHO_ESX=1 VIRTWHO_ESX_OWNER=ACME_Corporation VIRTWHO_ESX_ENV=env1 VIRTWHO_ESX_SERVER=10.66.13.216 VIRTWHO_ESX_USERNAME=<username> VIRTWHO_ESX_PASSWORD=<password> 2. Add a new RHEL guest via VClient on ESX host 3. Check the log file /var/log/rhsm/rhsm.log Actual results: There's error log of virt-who: 2012-09-29 01:48:29,514 [ERROR] @virt-who.py:180 - Error in communication with virt backend, trying to recover: Traceback (most recent call last): File "/usr/share/virt-who/virt-who.py", line 174, in _send virtualGuests = self.virt.getHostGuestMapping() File "/usr/share/virt-who/vsphere.py", line 230, in getHostGuestMapping self.scan() File "/usr/share/virt-who/vsphere.py", line 185, in scan for propSet in obj.propSet: AttributeError: ObjectContent instance has no attribute 'propSet' Expected results: There should not be any error log info. Additional info:
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux.
This bug should be fixed (as well as couple others) in later versions of virt-who. I suggest to do a rebase in rhel-5.11.
Fixed in virt-who-0.9-1.el5.
Verified it on virt-who-0.9-2.el5 Steps to Verify: 1. configure the virt-who with the following parameters and restart service virt-who: VIRTWHO_BACKGROUND=1 VIRTWHO_DEBUG=1 VIRTWHO_INTERVAL=2 VIRTWHO_ESX=1 VIRTWHO_ESX_OWNER=ACME_Corporation VIRTWHO_ESX_ENV=Library VIRTWHO_ESX_SERVER=10.66.78.16 VIRTWHO_ESX_USERNAME=Administrator VIRTWHO_ESX_PASSWORD=qwer1234P! 2. Add a new RHEL guest via VClient on ESX host 3. Check the log file /var/log/rhsm/rhsm.log 2014-04-24 04:11:56,569 [DEBUG] @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [564d1f59-71c6-57c8-62f0-607a7218d24c], 44454c4c-4200-1034-8039-b8c04f503258: []} 2014-04-24 04:12:10,547 [DEBUG] @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [4200da77-c8af-c013-daef-7c0b7644e016, 564d1f59-71c6-57c8-62f0-607a7218d24c], 44454c4c-4200-1034-8039-b8c04f503258: []} Result:It hasn't generate error log as the bug description, And it send the correct host/guest to SAM server ,Therefore, verify it on virt-who-0.9-2.el5
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-1206.html