Bug 908954 - Release version is set to nothing instead of "Not Set" in gui
Summary: Release version is set to nothing instead of "Not Set" in gui
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: subscription-manager
Version: 5.10
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: beta
: 5.10
Assignee: Bryan Kearney
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel510 rhsm-2013
TreeView+ depends on / blocked
 
Reported: 2013-02-07 21:26 UTC by J.C. Molet
Modified: 2013-09-30 22:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
No description necessary
Clone Of:
Environment:
Last Closed: 2013-09-30 22:56:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
RHEL-7-GUI-Preference (240.38 KB, image/png)
2013-03-13 15:37 UTC, Sharath Dwaral
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1332 0 normal SHIPPED_LIVE subscription-manager bug fix and enhancement update 2013-09-30 22:49:24 UTC

Description J.C. Molet 2013-02-07 21:26:10 UTC
Description of problem:
In the system preferences dialog of subscription-manager-gui, the release version is not set to anything, when it should display as "Not Set"

Version-Release number of selected component (if applicable):
subscription-manager-gui-1.8.0-1.git.118.3f0cf12.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. Open subscription-manager-gui
2. Go to System > Preferences when your release is unset
  
Actual results:
The release is set to nothing in the drop down.  From what I can tell it is set to a python's None value.  When you click on the drop down, and select the nothing again, it will change to 'Not Set'.

Expected results:
This drop down should always display 'Not Set' when there is no release set.

Additional info:
I'm testing this off of a stand alone candlepin with standard TESTDATA loaded.

Comment 2 Bryan Kearney 2013-02-11 16:30:35 UTC
commit 94540bcee9b9f9a777d45bb67989d4fb2eb0dcb9
Author: Bryan Kearney <bkearney>
Date:   Fri Feb 8 16:36:21 2013 -0500

    908954: Ensure that 'Not Set' is shown in the preferences dialog if it is not set

Comment 3 Sharath Dwaral 2013-03-12 20:24:41 UTC
rpm -qa | egrep "subscription-manager|python-rhsm"
subscription-manager-gui-1.8.4-1.git.17.db21599.el6.x86_64
python-rhsm-1.8.7-1.git.1.675a611.el6.x86_64
subscription-manager-migration-1.8.4-1.git.17.db21599.el6.x86_64
subscription-manager-firstboot-1.8.4-1.git.17.db21599.el6.x86_64
subscription-manager-migration-data-1.12.2.6-1.git.0.171d4c3.el6.noarch
subscription-manager-1.8.4-1.git.17.db21599.el6.x86_64

Verified on RHEL 6.4 with the above package. 

Waiting to verify the same on RHEL 7.0 as GUI is not working

Comment 4 Sharath Dwaral 2013-03-13 15:37:58 UTC
Created attachment 709667 [details]
RHEL-7-GUI-Preference

# rpm -qa | egrep "subscription-manager|python-rhsm"
subscription-manager-firstboot-1.8.4-1.el7.x86_64
python-rhsm-1.8.7-1.el7.x86_64
subscription-manager-1.8.4-1.el7.x86_64
subscription-manager-debuginfo-1.8.4-1.el7.x86_64
subscription-manager-gui-1.8.4-1.el7.x86_64
subscription-manager-migration-1.8.4-1.el7.x86_64


Verified on RHEL 7.0

Comment 5 RHEL Program Management 2013-04-09 20:52:27 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 7 errata-xmlrpc 2013-09-30 22:56:07 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-2013-1332.html


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