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.
Bug 1437229 - Show "NameError: global name 'virt' is not defined" when remote libvirt mode with hypervisor = hwuuid
Summary: Show "NameError: global name 'virt' is not defined" when remote libvirt mode ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who
Version: 7.3
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Chris Snyder
QA Contact: Eko
URL:
Whiteboard:
Depends On: 1403640
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-29 20:14 UTC by Kevin Howell
Modified: 2019-10-28 07:21 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1403640
Environment:
Last Closed: 2017-08-01 19:24:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github virt-who virt-who pull 56 0 None None None 2017-03-29 20:14:48 UTC
Red Hat Product Errata RHBA-2017:2084 0 normal SHIPPED_LIVE virt-who bug fix and enhancement update 2017-08-01 18:14:28 UTC

Comment 3 Eko 2017-03-30 01:52:05 UTC 
according to the "man virt-who-config" defined, hwuuid for hypervisor_id only support esx and rhevm, but our test results show hwuuid can support: esx, rhevm, xen,  can't support libvirt(remote), hyper-v,


hypervisor_id
   Property  that should be used as identification of the hypervisor. Can be one of following: uuid, hostname, hwuuid. Note that some virtualization backends don't have all of them implemented. Default is uuid. hwuuid is applicable to esx and rhevm only. This property is meant to be set up before initial run of virt-who. Changing it later will result in duplicated entries in the subscription manager.
Comment 5 yuefliu 2017-04-28 03:16:33 UTC 
By check the bug on RHEL-7.4-20170426.4-Server-x86_64 with virt-who-0.19-4, it is also failed to get and send remote libvirt mapping info to Stage Candleping/satellite6.2.8 with 'hypervisor_id=hwuuid', the rhsm log is:

-----rhsm.log----
2017-04-27 23:12:21,375 [virtwho.stage-libvirt ERROR] MainProcess(8156):Thread-2 @virt.py:run:383 - Thread 'stage-libvirt' fails with error: Invalid option hwuuid for hypervisor_id, use one of: uuid, or hostname
2017-04-27 23:12:21,375 [virtwho.stage-libvirt INFO] MainProcess(8156):Thread-2 @virt.py:_send_data:833 - Report for config "stage-libvirt" gathered, placing in datastore
2017-04-27 23:12:21,375 [virtwho.stage-libvirt INFO] MainProcess(8156):Thread-2 @virt.py:run:407 - Waiting 60 seconds before performing action again 'stage-libvirt'
2017-04-27 23:12:22,096 [virtwho.destination_-761514034043212611 DEBUG] MainProcess(8156):Thread-3 @virt.py:_send_data:566 - ErrorReport received for source: stage-libvirt
Comment 7 Liushihui 2017-06-08 08:11:31 UTC 
It still exist on virt-who-0.19-2.el6sat.noarch
Comment 8 errata-xmlrpc 2017-08-01 19:24:47 UTC 
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://access.redhat.com/errata/RHBA-2017:2084
Note You need to log in before you can comment on or make changes to this bug.