Bug 845265

Summary:	[RFE] practical use of the proxy options to subscription-manager modules
Product:	Red Hat Enterprise Linux 7	Reporter:	John Sefler <jsefler>
Component:	subscription-manager	Assignee:	candlepin-bugs
Status:	CLOSED WONTFIX	QA Contact:	IDM QE LIST <seceng-idm-qe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	bkearney, jesusr
Target Milestone:	beta	Keywords:	FutureFeature
Target Release:	7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-08-06 15:05:11 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:	863175

Description John Sefler 2012-08-02 13:52:53 UTC

Description of problem:
Many of the subscription-manager CLI modules have optional parameters for --proxy --proxyuser and --proxypassword.  When using these parameters on the command line, they are NOT persisted to the rhsm.conf file.  Instead, they override their corresponding values set in the rhsm.conf.  While I believe this is the correct behavior for an optional cli argument, it is not practical and it is NOT how rhnreg_ks handles the proxy options.  Like rhnreg_ks, it is more practical to persist the value of the specified proxy options to the rhsm.conf file when used during a call to subscription-manager register.

If you agree with these statements and decide to fix this bug, then I also believe you should apply the the same fixes as detailed in Bug 842768 and limit the --proxy --proxyuser and --proxypassword options to these modules:
  register
  redeem
  orgs
  environments
  service-level


Version-Release number of selected component (if applicable):
[root@jsefler-rhel59 ~]# rpm -q subscription-manager
subscription-manager-1.0.11-1.git.11.4d6cb5a.el5

Comment 1 RHEL Program Management 2012-08-02 14:09:03 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 3 Jesus M. Rodriguez 2013-08-06 15:05:11 UTC

(In reply to John Sefler from comment #0)
> Description of problem:
> Many of the subscription-manager CLI modules have optional parameters for
> --proxy --proxyuser and --proxypassword.  When using these parameters on the
> command line, they are NOT persisted to the rhsm.conf file.  Instead, they
> override their corresponding values set in the rhsm.conf.  While I believe
> this is the correct behavior for an optional cli argument, it is not
> practical and it is NOT how rhnreg_ks handles the proxy options.  Like
> rhnreg_ks, it is more practical to persist the value of the specified proxy
> options to the rhsm.conf file when used during a call to
> subscription-manager register.

No I do not think they should be persisted when you pass them in as optional parameters to these commands.

> 
> If you agree with these statements and decide to fix this bug, then I also
> believe you should apply the the same fixes as detailed in Bug 842768 and
> limit the --proxy --proxyuser and --proxypassword options to these modules:
>   register
>   redeem
>   orgs
>   environments
>   service-level

No because the others listed in the bug #842768 require internet connectivity therefore should also have the parameters just in case.