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:
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.
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
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" } } ]