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.
On the rhel7.1, the version of component should be as the following:
subscription-manager-1.13.5-1.el7.x86_64
python-rhsm-1.13.5-1.el7.x86_64
virt-who-0.11-2.el7.noarch
katello-headpin-1.4.3.28-1.el6sam_splice.noarch
candlepin-0.9.6.5-1.el6sam.noarch
It's a little bit more complicated now, virt-who can now has more than one backend enabled.
I would suggest following info output for each config:
Using configuration "<name>" ("<mode>" mode).
For example:
Using configuration "esx test" ("esx" mode).
Using configuration "hyperv test" ("hyperv" mode).
Using commandline or sysconfig configuration ("libvirt" mode).
Is this agreeable? Suggestions of better format welcomed :)
Verified it on virt-who-0.11-3.el7.noarch
Verified process
1. Register system to SAM server
2. Configure virt-who run at libvirt mode
3. Check virt-who 's log , it will show virt-who run at (libvirt mode):
2014-11-12 16:45:23,914 [INFO] @virtwho.py:453 - No configurations found, using libvirt as backend
2014-11-12 16:45:23,914 [INFO] @virtwho.py:460 - Using configuration "virt-who" ("libvirt" mode)
2014-11-12 16:45:23,914 [DEBUG] @virtwho.py:170 - Starting infinite loop with 5 seconds interval
2014-11-12 16:45:23,950 [DEBUG] @libvirtd.py:95 - Starting libvirt monitoring event loop
2014-11-12 16:45:23,951 [INFO] @libvirtd.py:187 - Using libvirt url: ""
2014-11-12 16:45:24,066 [INFO] @subscriptionmanager.py:109 - Sending list of uuids: []
4.Configure virt-who run at esx mode.
5.Check the virt-who's log, it will show virt-who run at (esx mode):
2014-11-12 16:46:54,386 [INFO] @virtwho.py:458 - Using commandline or sysconfig configuration ("esx" mode)
2014-11-12 16:46:54,387 [DEBUG] @virtwho.py:170 - Starting infinite loop with 5 seconds interval
As virt-who can show the run mode in the log, verify it in this version.
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