Hide Forgot
Description of problem: When virt-who run at rhevm or vdsm mode, it can't get hypervisorVersion. Version-Release number of selected component (if applicable): virt-who-0.16-7.el6 subscription-manager-1.16.8-7.el6.x86_64 python-rhsm-1.16.6-1.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Register system to satellite 2. Configure virt-who run at vdsm mode, Then restart virt-who service and check virt-who's log 2016-03-24 23:44:39,142 [virtwho.main DEBUG] MainProcess(16380):MainThread @subscriptionmanager.py:sendVirtGuests:148 - Domain info: [ { "guestId": "04c1acbb-239c-4ae6-886d-31dcd8a60c06", "state": 1, "attributes": { "active": 1, "hypervisorVersion": "", ==========It's null "virtWhoType": "vdsm", "hypervisorType": "qemu" } } ] 3. Configure virt-who run at rhevm mode, Then restart virt-who service and check virt-who's log 2016-03-24 23:44:06,747 [virtwho.main DEBUG] MainProcess(16293):MainThread @subscriptionmanager.py:hypervisorCheckIn:186 - Host-to-guest mapping: { "d8134060-415b-46c0-a7ce-37fd9df48884": [], "ab0866e8-2c99-4704-901b-fb1d979387f3": [ { "guestId": "a11f0b29-b430-4a53-978a-cae879ad1ef3", "state": 2, "attributes": { "active": 0, "hypervisorVersion": "", =============It's null "virtWhoType": "rhevm", "hypervisorType": "qemu" } } ] } Actual results: The "hypervisorVersion" is null when virt-who run at vdsm and rhevm mode Expected results: It should get "hypervisorVersion" when virt-who run at vdsm and rhevm mode Additional info: When virt-who work at libvirt mode, it can get "hypervisorVersion" 2016-03-24 23:51:06,254 [virtwho.main DEBUG] MainProcess(16955):MainThread @subscriptionmanager.py:sendVirtGuests:148 - Domain info: [ { "guestId": "04c1acbb-239c-4ae6-886d-31dcd8a60c06", "state": 1, "attributes": { "active": 1, "hypervisorVersion": "0.12.1", =====It can show "hypervisorVersion" "virtWhoType": "libvirt", "hypervisorType": "QEMU" } } ]
Support for reporting version of RHEVM is already present upstream, but reporting for vdsm (and local libvirt) doesn't make sense any more. The hypervisor type and version is now reported as hypervisor fact instead of guest attribute, so in non-remote mode (libvirt and vdsm) it won't be reported (no information about host is reported). See bug 1322859.
Fixed in virt-who-0.18-1.el6.
verified in virt-who-0.18-1.el6 for local mode (libvirt, vdsm), virt-who won't support to print the hypervisor type and version again. 2016-12-06 21:48:56,469 [virtwho.main DEBUG] MainProcess(31072):MainThread @main.py:_main:232 - Associations found: { "hypervisors": [ { "guests": [ { "attributes": { "active": 1, "virtWhoType": "vdsm" }, "guestId": "c2303f4f-0971-43f7-8775-775785b8e7fe", "state": 1 } ] } ] }
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/RHBA-2017-0675.html