Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1168122 - virt-who incorrectly says that VM is from 'None' hypervisor
virt-who incorrectly says that VM is from 'None' hypervisor
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who (Show other bugs)
7.1
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Radek Novacek
Li Bin Liu
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-26 03:17 EST by Radek Novacek
Modified: 2016-11-30 19:33 EST (History)
3 users (show)

See Also:
Fixed In Version: virt-who-0.11-5.el7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-05 05:23:59 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0430 normal SHIPPED_LIVE Moderate: virt-who security, bug fix, and enhancement update 2015-03-05 09:52:46 EST

  None (edit)
Description Radek Novacek 2014-11-26 03:17:04 EST
Copied from bug 1158859#c6:


But we have another problem introduced with this update: 

** In the previous version of virt-who (virt-who-0.8-15.el7_0.noarch), the hypervisors were named according to their type - e.g. "esx hypervisor ABCDE..." and "rhevm hypervisor FGHIJ...". Please see the name below - "esx hypervisor 30303...." and the attachment "virt-who-0.8-15.el7.png" for their naming convention in Satellite 5 GUI.

----8<----------

DEBUG: Sending plan: [[0, 'exists', 'system', {'uuid': '0000000000000000', 'identity': 'host'}], [0, 'crawl_began', 'system', {}], [0, 'exists', 'domain', {'state': 'running', 'memory_size': 0, 'name': u'VM from esx hypervisor 30303734-3536-5a43-3233-303130364c34' ...

----8<----------

** When using this new version (virt-who-0.11-4.el7.noarch.rpm) both esx and rhevm hypervisors are named as "None hypervisor". Again, please see name below - "None hypervisor 30303...." and the attachment "virt-who-0.11-4.el7.png" for their naming convention in Satellite 5 GUI.   

----8<----------

DEBUG: Sending plan: [[0, 'exists', 'system', {'uuid': '0000000000000000', 'identity': 'host'}], [0, 'crawl_began', 'system', {}], [0, 'exists', 'domain', {'state': 'running', 'memory_size': 0, 'name': u'VM from None hypervisor 30303734-3536-5a43-3233-303130364c34'

----8<----------
Comment 1 Radek Novacek 2014-11-26 03:21:31 EST
Fix for this issue has been applied upstream:

https://git.fedorahosted.org/cgit/virt-who.git/commit/?id=2a44c5e74487f454ee3140231edcab9c946522d2
Comment 2 Ekin Meroglu 2014-11-26 15:51:21 EST
Hi,

I've tested the git version, both issues seems fixed - thanks...
Comment 3 Radek Novacek 2014-11-28 06:19:50 EST
Fixed in virt-who-0.11-5.el7.
Comment 5 Liushihui 2015-01-04 02:15:49 EST
Verify it on virt-who-0.11-5.el7.

Version-Release number of selected component (if applicable):
[root@hp-z220-04 virt-who]# rpm -q virt-who
virt-who-0.11-5.el7.noarch

Verify process:
1.Register to satellite5.6/Satellite6.10
2.Configure virt-who run at esx mode:
# cat /etc/sysconfig/virt-who
VIRTWHO_DEBUG=1
VIRTWHO_BACKGROUND=1
VIRTWHO_INTERVAL=10
VIRTWHO_SATELLITE=1
VIRTWHO_ESX=1
VIRTWHO_ESX_OWNER=ACME_Corporation
VIRTWHO_ESX_ENV=Library
VIRTWHO_ESX_SERVER=10.66.78.75
VIRTWHO_ESX_USERNAME=Administrator@vsphere.local
VIRTWHO_ESX_PASSWORD=qwer1234P!
VIRTWHO_SATELLITE_SERVER=http://10.66.128.29/XMLRPC
VIRTWHO_SATELLITE_USERNAME=admin
VIRTWHO_SATELLITE_PASSWORD=admin
# service virt-who restart
3. Open satellite web UI, it can show esx hypervisor type under system-->Physical Systems/Virtual Systems
"esx hypervisor aee4ff00-8c33-11e2-994a-6c3be51d959a"
Comment 7 errata-xmlrpc 2015-03-05 05:23:59 EST
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/RHSA-2015-0430.html

Note You need to log in before you can comment on or make changes to this bug.