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 800459 - subscription-manager config removes the value from /etc/rhsm/rhsm.conf file if the value is not specified
Summary: subscription-manager config removes the value from /etc/rhsm/rhsm.conf file i...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: William Poteat
QA Contact: Entitlement Bugs
URL:
Whiteboard:
Depends On:
Blocks: 771481
TreeView+ depends on / blocked
 
Reported: 2012-03-06 14:08 UTC by Shwetha Kallesh
Modified: 2012-12-05 20:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-05 20:45:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Shwetha Kallesh 2012-03-06 14:08:06 UTC 
Description of problem:

subscription-manager config removes the value from /etc/rhsm/rhsm.conf file if the value is not specified

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

[root@dhcp201-162 ~]# subscription-manager config --server.hostname=
[root@dhcp201-162 ~]# cat /etc/rhsm/rhsm.conf | grep hostname
# Server hostname:
hostname=

  
Actual results:
It removes the value completely

Expected results:
Should either set to default value and display a message saying "set to default value" or throw an error message saying "value is not specified"

Additional info:
Comment 4 RHEL Program Management 2012-07-10 08:48:05 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 5 RHEL Program Management 2012-07-11 01:48:26 UTC 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 6 Devan Goodwin 2012-12-05 20:31:57 UTC 
Can I propose that we leave the old behaviour in place, I think I honestly prefer it and it makes more sense.

If I run the config command and tell it to set a value, it should get set to whatever I specify.

The default rhsm.conf has four empty properties by default (proxy settings). With this change, if we were to modify one, we can't unset it unless we take it out of the config entirely, whereas previously we could. Once it's gone from the config file it starts getting pretty hard to remember just what properties are supported and which aren't.

I can't see any gain here, we may very well have config properties we want to set as empty, why block it from CLI?
Comment 7 Devan Goodwin 2012-12-05 20:45:13 UTC 
Spoke with zeus and jsefler who are agreed the old behaviour is probably preferable, as we do make use of empty properties quite regularly.
Note You need to log in before you can comment on or make changes to this bug.