Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 990957

Summary: virt-who creat a null system in SAM server in esx mode
Product: Red Hat Enterprise Linux 5 Reporter: gaoshang <sgao>
Component: virt-whoAssignee: Radek Novacek <rnovacek>
Status: CLOSED ERRATA QA Contact: Entitlement Bugs <entitlement-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.10CC: liliu, ovasik, qianzhan, shihliu
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: virt-who-0.9-1.el5 Doc Type: Bug Fix
Doc Text:
no docs needed
 Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-16 00:29:16 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:
Attachments:
Description Flags
null_system_in_sam none

Description gaoshang 2013-08-01 09:40:20 UTC 
Description of problem:
Configure virt-who in esx mode and set VIRTWHO_INTERVAL=5, keep virt-who running, then add an esx host to vCenter, it'll take few minutes for adding esx host finished, during this period, virt-who creat a null system in SAM server.

Version-Release number of selected component (if applicable):
virt-who-0.7-9.el5

How reproducible:
always

Steps to Reproduce:
1. Configure virt-who in esx mode and set VIRTWHO_INTERVAL=5, start virt-who service.
2. Add an esx host to vCenter via vClient, it'll take few minutes to finished.
3. Check the log in /var/log/rhsm/rhsm.log and systems in SAM server.

Actual results:
null system has been added to SAM server. Please the the log info:

2013-08-01 05:04:28,181 [WARNING]  @virt-who.py:418 - Listening for events is not available in VDSM or ESX mode
2013-08-01 05:04:45,787 [DEBUG]  @virt-who.py:431 - Virt-who is running in esx mode
2013-08-01 05:04:45,788 [DEBUG]  @virt-who.py:438 - Starting infinite loop with 5 seconds interval and event handling
2013-08-01 05:04:47,192 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {44454c4c-4200-1034-8039-b8c04f503258: [564d57eb-6ae8-4652-a883-25289f5f1e6d]}
... 

2013-08-01 05:06:03,549 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {44454c4c-4200-1034-8039-b8c04f503258: [564d57eb-6ae8-4652-a883-25289f5f1e6d]}
2013-08-01 05:06:11,992 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {None: [], 44454c4c-4200-1034-8039-b8c04f503258: [564d57eb-6ae8-4652-a883-25289f5f1e6d]}
-------------------------------------------------------------------------------------------
2013-08-01 05:06:12,637 [INFO]  @virt-who.py:200 - Created host: null with guests: []
-------------------------------------------------------------------------------------------
2013-08-01 05:06:19,049 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {None: [], 44454c4c-4200-1034-8039-b8c04f503258: [564d57eb-6ae8-4652-a883-25289f5f1e6d]}
2013-08-01 05:06:25,349 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {None: [], 44454c4c-4200-1034-8039-b8c04f503258: [564d57eb-6ae8-4652-a883-25289f5f1e6d]}
2013-08-01 05:06:31,733 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {None: [], 44454c4c-4200-1034-8039-b8c04f503258: [564d57eb-6ae8-4652-a883-25289f5f1e6d]}
2013-08-01 05:06:38,489 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {None: [], 44454c4c-4200-1034-8039-b8c04f503258: [564d57eb-6ae8-4652-a883-25289f5f1e6d]}
2013-08-01 05:06:44,788 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {None: [], 44454c4c-4200-1034-8039-b8c04f503258: [564d57eb-6ae8-4652-a883-25289f5f1e6d]}
2013-08-01 05:06:51,451 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {None: [], 44454c4c-4200-1034-8039-b8c04f503258: [564d57eb-6ae8-4652-a883-25289f5f1e6d]}
2013-08-01 05:06:58,348 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {None: [], 44454c4c-4200-1034-8039-b8c04f503258: [564d57eb-6ae8-4652-a883-25289f5f1e6d]}
2013-08-01 05:07:05,872 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {44454c4c-4c00-1031-8053-b8c04f4e3258: [], 44454c4c-4200-1034-8039-b8c04f503258: [564d57eb-6ae8-4652-a883-25289f5f1e6d]}
2013-08-01 05:07:07,163 [INFO]  @virt-who.py:200 - Created host: 44454c4c-4c00-1031-8053-b8c04f4e3258 with guests: []
2013-08-01 05:07:13,331 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {44454c4c-4c00-1031-8053-b8c04f4e3258: [], 44454c4c-4200-1034-8039-b8c04f503258: [564d57eb-6ae8-4652-a883-25289f5f1e6d]}
...

Expected results:
There should be a check when created host in SAM server, null system should not be added.

Additional info:
Comment 1 gaoshang 2013-08-01 09:42:48 UTC 
Created attachment 781504 [details]
null_system_in_sam

null_system_in_sam
Comment 2 Radek Novacek 2013-08-01 09:51:50 UTC 
This should be easy fix, just to filter out hosts with UUID == None.
Comment 3 Liushihui 2013-10-15 02:41:54 UTC 
This bug also exist on Rhel6.5 + ESX4.1
version :virt-who-0.8-9.el6.noarch
Comment 4 RHEL Program Management 2014-01-22 16:28:59 UTC 
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.
Comment 5 Liushihui 2014-03-13 06:08:34 UTC 
Do the same test under the Rhel7-20140305.0+ESX5.5 against stage candlepin, it has the same problem.

Version-Release number of selected component:
subscription-manager-1.10.14-4.el7.x86_64
python-rhsm-1.10.12-1.el7.x86_64
virt-who-0.8-12.el7.noarch
Comment 6 Radek Novacek 2014-03-13 13:43:55 UTC 
For RHEL-5 this is fixed in virt-who-0.9-1.el5. Please create separate bugs for RHEL-6 and RHEL-7.
Comment 8 Liushihui 2014-04-24 09:00:17 UTC 
Verified it on virt-who-0.9-2.el5

Verified steps:
1.Configure virt-who
#vim /etc/sysconfig/virt-who, Update as the following:
VIRTWHO_DEBUG=1
VIRTWHO_INTERVAL=5
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.Register to SAM server
#subscription-manager register --username=admin --password=admin
3.Restart virt-who service
# service virt-who restart
4.Add an esx host to vCenter via vClient, it'll take few minutes to finished.
5.Check the virt-who log in the rhsm.log file, 
#tail -f /var/log/rhsm/rhsm.log
6.Check the SAM web UI

Result:
After step5, it hasn't generate a NULL system
2014-04-24 03:43:33,846 [WARNING]  @virt-who.py:515 - Listening for events is not available in VDSM, ESX, RHEV-M or Hyper-V mode
2014-04-24 03:43:34,103 [DEBUG]  @virt-who.py:528 - Virt-who is running in esx mode
2014-04-24 03:43:34,103 [DEBUG]  @virt-who.py:535 - Starting infinite loop with 5 seconds interval and event handling
2014-04-24 03:43:41,006 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [564d1f59-71c6-57c8-62f0-607a7218d24c]}
2014-04-24 03:43:44,619 [INFO]  @virt-who.py:217 - Created host: 20ef5325-a91f-4d57-ba67-9ca31a75c5f6 with guests: [564d1f59-71c6-57c8-62f0-607a7218d24c]
2014-04-24 03:43:59,643 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [564d1f59-71c6-57c8-62f0-607a7218d24c]}
2014-04-24 03:44:14,967 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [564d1f59-71c6-57c8-62f0-607a7218d24c]}
2014-04-24 03:44:33,217 [DEBUG]  @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {aee4ff00-8c33-11e2-994a-6c3be51d959a: [564d1f59-71c6-57c8-62f0-607a7218d24c]}
2014-04-24 03:44:49,127 [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 03:44:58,645 [INFO]  @virt-who.py:217 - Created host: 1e9cabd9-2e2e-4c6f-98ba-aad894257f1e with guests: []
2014-04-24 03:45:14,791 [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 03:45:30,554 [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: []}
After step6, it also hasn't displayed a NULL system in the SAM web UI.
Therefore, this bug can't reproduce on the virt-who-0.9-2.el5.
Comment 10 errata-xmlrpc 2014-09-16 00:29:16 UTC 
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