Bug 1254353

Summary: unexpected "Registering to: hostname:port/prefix" when calling subscription-manager orgs
Product: Red Hat Enterprise Linux 7 Reporter: John Sefler <jsefler>
Component: subscription-managerAssignee: vritant <vrjain>
Status: CLOSED DUPLICATE QA Contact: John Sefler <jsefler>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: vrjain
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: 2015-08-27 18:20:14 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:

Description John Sefler 2015-08-17 20:07:22 UTC 
Description of problem:
As a side affect of https://bugzilla.redhat.com/show_bug.cgi?id=985157#c13 we now get an additional stdout message when executing subscription-manager orgs module stating ...
Registering to: hostname:port/prefix

Version-Release number of selected component (if applicable):
[root@jsefler-7 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 2.0.6-1
subscription management rules: 5.16
subscription-manager: 1.15.9-6.el7
python-rhsm: 1.15.4-2.el7

How reproducible:


Steps to Reproduce:
[root@jsefler-7 ~]# subscription-manager config --server.hostname=subscription.rhn.stage.redhat.com --server.port=443 --server.prefix=/subscription
[root@jsefler-7 ~]# 
[root@jsefler-7 ~]# subscription-manager orgs
Registering to: subscription.rhn.stage.redhat.com:443/subscription <=== UNEXPECTED
Username: stage_test_12
Password: 
+-------------------------------------------+
          stage_test_12 Organizations
+-------------------------------------------+

Name: 7608122
Key:  7608122


Actual results:
  above

Expected results:
  the stdout from calls to the orgs module should exclude "Registering to:" message

Additional info:
Comment 1 vritant 2015-08-27 18:20:14 UTC 

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