RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 845265 - [RFE] practical use of the proxy options to subscription-manager modules
Summary: [RFE] practical use of the proxy options to subscription-manager modules
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: 7.0
Assignee: candlepin-bugs
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel70
TreeView+ depends on / blocked
 
Reported: 2012-08-02 13:52 UTC by John Sefler
Modified: 2013-08-06 15:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-06 15:05:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.