Bug 1048954
Summary: | virt-who in rhel7 needs to report which libvirt guests are active | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Carter Kozak <ckozak> |
Component: | virt-who | Assignee: | Radek Novacek <rnovacek> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | gaoshang <sgao> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.0 | CC: | bkearney, ckozak, ovasik, shihliu, svenkatr |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | virt-who-0.8-12.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-06-13 10:51:31 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: |
Description
Carter Kozak
2014-01-06 15:40:32 UTC
It looks like we might need to rev the required version of python-rhsm for this to prevent us from breaking old candlepin servers with excess data. I'll post a version when I can, I'll do a new rhel7 build of python-rhsm The updated virt-who should depend on python-rhsm-1.10.10 Let me know if there's anything you need. This feature has been added upstream: https://git.fedorahosted.org/cgit/virt-who.git/commit/?h=systemd&id=2ac716f84d87dc75898bd5b24bf56ee159a688a4 This has been added in virt-who-0.8-12.el7. It only has been fixed on libvirt mode (qemu/kvm), please see the following "Test process 2" ,But under the ESX mode, it still does not support new virt-guest active state reporting, please see the following "Test process 1" Version-Release number of selected component (if applicable): virt-who-0.8-12.el7.noarch python-rhsm-1.10.10-1.el7.x86_64 Test process 1(incorrect): RHEL-7.0-20140116.1-Server-x86_64+ ESX5.5 against SAM-1.3.1-RHEL-6-20131219.1 Precondition: Prepare RHEL7.0 with latest subscription-manager and virt-who installed. ESX host has been added to vcenter, two guest have been run on ESX host2 Our test env as the following: vCenter: 10.66.78.16 ESX host 1: 10.66.13.181 ESX host 2: 10.66.13.187 Test step: 1. Configure virt-who run at the ESX mode #vim /etc/sysconfig/virt-who VIRTWHO_DEBUG=1 VIRTWHO_INTERVAL=10 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! # systemctl restart virt-who 2. Register the RHEL7.0 to SAM server # Subscription-manager register --username=admin --password=admin 3. Register one of the guest to SAM server 4. Check the virt-who log in the /etc/rhsm/rhsm.log, The virt-guest active state has been report. 2014-01-17 16:44:24,486 [WARNING] @virt-who.py:515 - Listening for events is not available in VDSM, ESX, RHEV-M or Hyper-V mode 2014-01-17 16:44:24,618 [DEBUG] @virt-who.py:528 - Virt-who is running in esx mode 2014-01-17 16:44:24,618 [DEBUG] @virt-who.py:535 - Starting infinite loop with 10 seconds interval and event handling 2014-01-17 16:44:31,909 [DEBUG] @subscriptionmanager.py:109 - Sending update in hosts-to-guests mapping: {44454c4c-4c00-1031-8053-b8c04f4e3258: [564d8a10-90eb-d40e-42ec-9ca700de054f, 42004d5f-71c0-bf98-b8e2-c914dd572560], 44454c4c-4200-1034-8039-b8c04f503258: []} Result: The virt-guest active state still hasn't been report in the virt-who log. Test process 2(correct) : RHEL-7.0-20140116.1-Server-x86_64(KVM) against SAM-1.3.1-RHEL-6-20131219.1 Test steps: 1. Configure virt-who run at the libvirt mode #vim /etc/sysconfig/virt-who VIRTWHO_DEBUG=1 VIRTWHO_INTERVAL=10 2. Register host and guest to SAM server 3. Check the virt-who log in the /etc/rhsm/rhsm.log 2014-01-17 16:39:18,915 [DEBUG] @virt.py:66 - Virtual machine found: 7.0_Server_x86_64: e29811e2-cbba-7f38-ec26-9e71d427ac7e 2014-01-17 16:39:18,916 [DEBUG] @subscriptionmanager.py:101 - Sending list of uuids: [{'guestId': 'e29811e2-cbba-7f38-ec26-9e71d427ac7e', 'attributes': {'active': 1, 'virtWhoType': 'libvirt', 'hypervisorType': 'QEMU'}, 'state': 1}] Result: The virt-guest active state has been report in the virt-who log. it should be correct. Carter, is it required to have guest status working on non-libvirt hypervisors? I vaguely recall that you said that it's sufficient to have it only on libvirt, right? For rhel 7 pricing I dont think we are required to get status/other attributes for non-libvirt. That said, it would be very helpful to have data for other hypervisors that mirrors what we're sending up for libvirt, if we can collect it. If it's not too much trouble and we can get it in now, it'll probably help out with things like satellite and katello. I don't think that we have enough time to implement and test this feature for all the hypervisors in time for RHEL-7.0. I'll create new bug targeted 7.1 requesting additional features. I have created bug 1056419 for tracking active guests support on other hypervisors than libvirt. Since that's not 7.0 stuff, I'll change this bug to request libvirt support only. As it has fixed on the libvirt mode, Verified it on virt-who-0.8-12.el7.noarch This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. |