Bug 848027

Summary:	Launching gui on a unregistered client displays the following on console "Error while checking server version: No such file or directory"
Product:	Red Hat Enterprise Linux 5	Reporter:	Shwetha Kallesh <skallesh>
Component:	subscription-manager	Assignee:	Bryan Kearney <bkearney>
Status:	CLOSED DUPLICATE	QA Contact:	Entitlement Bugs <entitlement-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.9	CC:	bkearney
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-17 16:49:52 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

Description Shwetha Kallesh 2012-08-14 11:07:06 UTC

Description of problem:
Launching gui on a unregistered client displays the following on console "Error while checking server version: No such file or directory"

Version-Release number of selected component (if applicable):
[root@dhcp201-115 ~]# rpm -qa | grep subscription-manager
subscription-manager-migration-1.0.13-1.git.20.5346dac.el5
subscription-manager-1.0.13-1.git.20.5346dac.el5
subscription-manager-gui-1.0.13-1.git.20.5346dac.el5
subscription-manager-migration-data-1.11.2.3-1.git.0.861f9ba.el5
subscription-manager-firstboot-1.0.13-1.git.20.5346dac.el5


How reproducible:

Steps to Reproduce:
1.[root@dhcp201-115 ~]# subscription-manager-gui
Error while checking server version: No such file or directory

User interrupted process.
[root@dhcp201-115 ~]# subscription-manager register --org=admin
Username: admin
Password: 
The system has been registered with id: 71c0ef9a-16c3-40de-8326-e039dbca6d69 
[root@dhcp201-115 ~]# subscription-manager-gui

2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Bryan Kearney 2012-08-17 16:49:52 UTC


*** This bug has been marked as a duplicate of bug 849022 ***