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:
virt-who failed to send host/guest info to Satellite when ESXi have no host at all, maybe Satellite missed to handle blank message.
Version-Release number of selected component (if applicable):
# rpm -qa | grep virt-who
virt-who-0.8-8.el6.noarch
How reproducible:
always
Steps to Reproduce:
1. Prepare ESXi with no host in it
2. Configure virt-who to connect to Satellite, set VIRTWHO_INTERVAL=5
3. Restart virt-who service
Actual results:
virt-who should send blank h/g info every 5 seconds
Expected results:
virt-who halt for Satellite
Additional info:
Log info for Satellite, virt-who hang up there even though VIRTWHO_INTERVAL=5:
2013-08-29 04:28:04,617 [WARNING] @virt-who.py:502 - Listening for events is not available in VDSM, ESX, RHEV-M or Hyper-V mode
2013-08-29 04:28:04,618 [DEBUG] @satellite.py:49 - Initializing satellite connection to https://10.16.64.212/XMLRPC
2013-08-29 04:28:04,618 [INFO] @satellite.py:55 - Initialized satellite connection
2013-08-29 04:28:09,811 [DEBUG] @virt-who.py:515 - Virt-who is running in esx mode
2013-08-29 04:28:09,812 [DEBUG] @virt-who.py:522 - Starting infinite loop with 5 seconds interval and event handling
By comparison, virt-who behaves in SAM:
2013-08-29 04:27:12,225 [WARNING] @virt-who.py:502 - Listening for events is not available in VDSM, ESX, RHEV-M or Hyper-V mode
2013-08-29 04:27:17,775 [DEBUG] @virt-who.py:515 - Virt-who is running in esx mode
2013-08-29 04:27:17,775 [DEBUG] @virt-who.py:522 - Starting infinite loop with 5 seconds interval and event handling
2013-08-29 04:27:17,821 [DEBUG] @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {}
2013-08-29 04:27:23,029 [DEBUG] @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {}
2013-08-29 04:27:28,233 [DEBUG] @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {}
Comment 2RHEL Program Management
2013-10-14 02:30:00 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
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: virt-who failed to send host/guest info to Satellite when ESXi have no host at all, maybe Satellite missed to handle blank message. Version-Release number of selected component (if applicable): # rpm -qa | grep virt-who virt-who-0.8-8.el6.noarch How reproducible: always Steps to Reproduce: 1. Prepare ESXi with no host in it 2. Configure virt-who to connect to Satellite, set VIRTWHO_INTERVAL=5 3. Restart virt-who service Actual results: virt-who should send blank h/g info every 5 seconds Expected results: virt-who halt for Satellite Additional info: Log info for Satellite, virt-who hang up there even though VIRTWHO_INTERVAL=5: 2013-08-29 04:28:04,617 [WARNING] @virt-who.py:502 - Listening for events is not available in VDSM, ESX, RHEV-M or Hyper-V mode 2013-08-29 04:28:04,618 [DEBUG] @satellite.py:49 - Initializing satellite connection to https://10.16.64.212/XMLRPC 2013-08-29 04:28:04,618 [INFO] @satellite.py:55 - Initialized satellite connection 2013-08-29 04:28:09,811 [DEBUG] @virt-who.py:515 - Virt-who is running in esx mode 2013-08-29 04:28:09,812 [DEBUG] @virt-who.py:522 - Starting infinite loop with 5 seconds interval and event handling By comparison, virt-who behaves in SAM: 2013-08-29 04:27:12,225 [WARNING] @virt-who.py:502 - Listening for events is not available in VDSM, ESX, RHEV-M or Hyper-V mode 2013-08-29 04:27:17,775 [DEBUG] @virt-who.py:515 - Virt-who is running in esx mode 2013-08-29 04:27:17,775 [DEBUG] @virt-who.py:522 - Starting infinite loop with 5 seconds interval and event handling 2013-08-29 04:27:17,821 [DEBUG] @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {} 2013-08-29 04:27:23,029 [DEBUG] @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {} 2013-08-29 04:27:28,233 [DEBUG] @subscriptionmanager.py:89 - Sending update in hosts-to-guests mapping: {}