Bug 849022

Summary: Error message appears in terminal when open subscription-manager gui from terminal if the system not registered
Product: Red Hat Enterprise Linux 5 Reporter: xingge <gxing>
Component: subscription-managerAssignee: Bryan Kearney <bkearney>
Status: CLOSED ERRATA QA Contact: Entitlement Bugs <entitlement-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.9CC: bkearney, khong, ldai, skallesh, spandey
Target Milestone: rcKeywords: QA-Closed
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-08 03:59:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 771748    
Attachments:
Description Flags
log when error happened none

Description xingge 2012-08-17 05:44:17 UTC 
Description of problem:
Error message appears in the terminal when open subscription-manager gui from the terminal by running command 'subscription-manager-gui' if the system is not registered.

Version-Release number of selected component (if applicable):
subscription-manager-firstboot-1.0.13-1.el5
subscription-manager-gui-1.0.13-1.el5
subscription-manager-1.0.13-1.el5
python-rhsm-1.0.5-1.el5

How reproducible:
always

Steps to Reproduce:
1.Make sure the system is not registered
2.open subscription-manager gui from terminal by:
#subscription-manager-gui
  
Actual results:
The subscription-manager-gui opens, and below errror message will show in terminal:
Error while checking server version: No such file or directory 

Expected results:
The subscription-manager-gui will open and no error appear in the terminal

Additional info:
1. Once the system registered then re-open the subscription-manager-gui as step 2 the error message will not appear
2. If register the system after above step 2, and then run the version command as below:
#subscription-manager version

then get this output - pls be noticed it shows 'Unknown' for the 'remote entitlement server' info:
remote entitlement server: Unknown
remote entitlement server type: subscription management service
subscription-manager: 1.0.13-1.el5
python-rhsm: 1.0.5-1.el5
Comment 1 RHEL Program Management 2012-08-17 05:56:57 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 2 xingge 2012-08-17 06:54:11 UTC 
Created attachment 605093 [details]
log when error happened
Comment 3 Bryan Kearney 2012-08-17 16:26:34 UTC 
I can not re-create, and there has been lots of work around version checking. Please re-verify with veriosn 1.0.14 or greater.
Comment 5 Bryan Kearney 2012-08-17 16:49:52 UTC 
*** Bug 848027 has been marked as a duplicate of this bug. ***
Comment 7 spandey 2012-08-23 16:04:01 UTC 
verified using following rpm 

subscription-manager-gui-1.0.14-1.git.20.7e3f72a.el5
subscription-manager-migration-data-1.11.2.3-1.git.0.861f9ba.el5
subscription-manager-firstboot-1.0.14-1.git.20.7e3f72a.el5
subscription-manager-migration-1.0.14-1.git.20.7e3f72a.el5
subscription-manager-1.0.14-1.git.20.7e3f72a.el5

Now version error is not getting displayed , working fine 
after register i got following message with version command 


[root@localhost ~]# subscription-manager version
registered to: 0.7.6-1
server type: subscription management service
subscription-manager: 1.0.14-1.git.20.7e3f72a.el5
python-rhsm: 1.0.5-1.git.1.1ce0910.el5


Working fine resolving defect as verified.
Comment 9 errata-xmlrpc 2013-01-08 03:59:12 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-0033.html