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 1308732 - subscription-manager system fact virt.uuid: Unknown is reported on physical systems
Summary: subscription-manager system fact virt.uuid: Unknown is reported on physical s...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.8
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-15 21:37 UTC by John Sefler
Modified: 2016-05-10 20:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-10 20:40:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0797 0 normal SHIPPED_LIVE python-rhsm and subscription-manager bug fix and enhancement update 2017-01-06 16:31:50 UTC

Description John Sefler 2016-02-15 21:37:36 UTC 
Description of problem:
Prior to subscription-manager commit f8416137a3b426aa54608116e005df7273abfada a physical system would not report a "virt.uuid" fact at all.  Now on the latest builds for rhel6.8, physical systems are reporting "virt.uuid: Unknown".

This may be an insignificant change, but it is a change.  Please advise whether I should update the automated test that caught this or you should fix the regression.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
Previous behavior from the subscription-manager on a physical ppc64 system on RHEL67...
[root@ibm-p8-05-lp7 ~]# rpm -q subscription-manager
subscription-manager-1.14.10-1.el6.ppc64
[root@ibm-p8-05-lp7 ~]# virt-what 
[root@ibm-p8-05-lp7 ~]# 
[root@ibm-p8-05-lp7 ~]# subscription-manager facts | grep virt
virt.host_type: Not Applicable
virt.is_guest: False
[root@ibm-p8-05-lp7 ~]# 

After upgrading to the subscription-manager targeted for release on RHEL68...
[root@ibm-p8-05-lp7 ~]# rpm -q subscription-manager
subscription-manager-1.16.8-2.el6.ppc64
[root@ibm-p8-05-lp7 ~]# virt-what 
[root@ibm-p8-05-lp7 ~]# 
[root@ibm-p8-05-lp7 ~]# subscription-manager facts | grep virtvirt.host_type: Not Applicable
virt.is_guest: False
virt.uuid: Unknown          <======== NEWLY ADDED AND UNEXPECTED
[root@ibm-p8-05-lp7 ~]# 


Actual results:
 above

Expected results:
 virt.uuid should only be shown when virt.is_guest: True

Additional info:


[root@ibm-p8-05-lp7 ~]# subscription-manager facts --list | grep proc_cpuinfo
proc_cpuinfo.common.machine: CHRP IBM,8247-22L
proc_cpuinfo.common.model: IBM,8247-22L
proc_cpuinfo.common.platform: pSeries

NEEDINFO: In light of recent LPAR work, maybe this ppc64 system is indeed a guest and virt-what is actually failing to report it.
Comment 2 Adrian Likins 2016-02-15 21:43:58 UTC 
pr at https://github.com/candlepin/subscription-manager/pull/1386

There can be cases where virt-what doesn't know the system is a virt guest, but we can find a virt.uuid anyway (ppc lpar mainly). This was changed as part of that, but the old behavior in this case is just as valid, so changing it back.

(ie, if we don't find a virt.uuid, don't add a 'virt.uuid' fact at all. Interim
was setting it to 'Unknown')l
Comment 6 Rehana 2016-02-25 07:49:48 UTC 
Reproducing the failure :
------------------------

[root@ibm-p8-05-lp5 ~]# rpm -q subscription-manager
subscription-manager-1.16.8-2.el6.ppc64


[root@ibm-p8-05-lp5 ~]# virt-what 

[root@ibm-p8-05-lp5 ~]#  subscription-manager facts | grep virt
virt.host_type: Not Applicable
virt.is_guest: False
virt.uuid: Unknown

[root@ibm-p8-05-lp5 ~]# subscription-manager facts --list | grep proc_cpuinfo
proc_cpuinfo.common.machine: CHRP IBM,8247-22L
proc_cpuinfo.common.model: IBM,8247-22L
proc_cpuinfo.common.platform: pSeries

With the updated subscription-manager packages:
-----------------------------------------------
[root@ibm-p8-05-lp6 ~]# virt-what 

[root@ibm-p8-05-lp6 ~]# subscription-manager facts | grep virt
virt.host_type: Not Applicable
virt.is_guest: False

[root@ibm-p8-05-lp6 ~]# rpm -q subscription-manager
subscription-manager-1.16.8-3.el6.ppc64

[root@ibm-p8-05-lp6 ~]# subscription-manager facts --list | grep proc_cpuinfo
proc_cpuinfo.common.machine: CHRP IBM,8247-22L
proc_cpuinfo.common.model: IBM,8247-22L
proc_cpuinfo.common.platform: pSeries

Marking the bug as verified!!
Comment 8 errata-xmlrpc 2016-05-10 20:40:37 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://rhn.redhat.com/errata/RHBA-2016-0797.html
Note You need to log in before you can comment on or make changes to this bug.