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 722248 - subscription-manager fact null value
Summary: subscription-manager fact null value
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: John Sefler
QA Contact: J.C. Molet
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel62
TreeView+ depends on / blocked
 
Reported: 2011-07-14 18:08 UTC by J.C. Molet
Modified: 2011-12-06 17:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 17:22:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
null value for dmi.processor.voltage is now reported as Unknown in the GUI (57.17 KB, image/png)
2011-08-08 13:44 UTC, John Sefler
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1695 0 normal SHIPPED_LIVE subscription-manager bug fix and enhancement update 2011-12-06 01:23:29 UTC

Description J.C. Molet 2011-07-14 18:08:12 UTC
Description of problem:
On some machines you are unable to determine some facts.  When read in by subscription manager, it doesn't set the values of these facts to anything.

Version-Release number of selected component (if applicable):
subscription-manager-gnome-0.96.4-1.git.4.f2638c9.el6.x86_64
subscription-manager-0.96.4-1.git.4.f2638c9.el6.x86_64
subscription-manager-firstboot-0.96.4-1.git.4.f2638c9.el6.x86_64
python-rhsm-0.96.7-1.git.3.f3ce5d1.el6.noarch


Steps to Reproduce:
1. register subscription-manager on a virtual machine
2. view the system facts either by the command line or the gui
  
Actual results:
dmi.processor.voltage has no value on the CLI.

In the GUI the value field for this fact is interpreted as a NULL.  This means for that row in the table, it only contains one column, and cannot be read the same way by accessibility programs.

Expected results:
If you run dmidecode manually from the command line it displays situations like this with the value "Unknown":

[root@jmolet-vm0 facts]# dmidecode | grep -i voltage
	Voltage: Unknown
	Voltage: Unknown

Subscription manager should also set these null fields to Unknown, so that the display of these values is more consistent with dmidecode.

Additional info:
There also seems to be several other inconsistencies.  For example when dmi.memory.speed is not specified it's value is " (ns)", where dmidecode and all other not specified fields display "Not Specified".

Comment 1 Bryan Kearney 2011-07-26 18:39:51 UTC
Fixed in master at b5346938bcd75b2a7be2c7f7ac9c432a3a62d60f. All blank strings are now Unknown.

Comment 3 Shwetha Kallesh 2011-07-27 07:27:37 UTC
The blank string still appears..

RPM's used:

subscription-manager-firstboot-0.96.4-1.git.64.b534693.el6.x86_64
subscription-manager-0.96.4-1.git.64.b534693.el6.x86_64
subscription-manager-gnome-0.96.4-1.git.64.b534693.el6.x86_64

Steps to reproduce :

subscription-manager register --username=admin --password=admin --org=admin
<shwetha> The system has been registered with id: 57b50403-1e5d-4749-adb3-7ee3cdb77639 
<shwetha> [root@sachbeta ~]#  subscription-manager facts --list | grep dmi.processor.voltage
<shwetha> dmi.processor.voltage:

Comment 4 Shwetha Kallesh 2011-07-27 07:29:52 UTC
Steps to reproduce :

subscription-manager register --username=admin --password=admin --org=admin
The system has been registered with id: 57b50403-1e5d-4749-adb3-7ee3cdb77639 

subscription-manager facts --list | grep dmi.processor.voltage
dmi.processor.voltage:

Comment 6 Bryan Kearney 2011-07-29 19:02:28 UTC
Fixed in 1deab574be7c57dd95e7f8ba7bc09fb83e0d12cd in master. Left is as cosmetic so that other tools can choose to display NULL differently.

Comment 7 Shwetha Kallesh 2011-08-01 09:27:25 UTC
Please move the bug to verified..

RPMs used :
subscription-manager-firstboot-0.96.4-1.git.70.a18d152.el6.x86_64
subscription-manager-gnome-0.96.4-1.git.70.a18d152.el6.x86_64
subscription-manager-0.96.4-1.git.70.a18d152.el6.x86_64

Steps to reproduce :

subscription-manager register --username=admin --password=admin --org=admin
The system has been registered with id: 737b4a42-e167-43b6-883e-6fa3b4811a14 

subscription-manager facts --list | grep dmi.processor.voltage


dmi.processor.voltage: Unknown

Comment 8 John Sefler 2011-08-08 13:44:41 UTC
Created attachment 517219 [details]
null value for dmi.processor.voltage is now reported as Unknown in the GUI

Also verifying the GUI....
[root@jsefler-onprem-62server ~]# rpm -q subscription-manager-gnome
subscription-manager-gnome-0.96.5-1.git.4.303423d.el6.x86_64

see voltage reported as "Unknown" in the screenshot

Comment 9 errata-xmlrpc 2011-12-06 17:22:21 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.

http://rhn.redhat.com/errata/RHBA-2011-1695.html


Note You need to log in before you can comment on or make changes to this bug.