Bug 800459
Summary: | subscription-manager config removes the value from /etc/rhsm/rhsm.conf file if the value is not specified | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Shwetha Kallesh <skallesh> |
Component: | subscription-manager | Assignee: | William Poteat <wpoteat> |
Status: | CLOSED NOTABUG | QA Contact: | Entitlement Bugs <entitlement-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3 | CC: | dgoodwin, wpoteat |
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-12-05 20:45:13 UTC | Type: | --- |
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: | 771481 |
Description
Shwetha Kallesh
2012-03-06 14:08:06 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. 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. 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? Spoke with zeus and jsefler who are agreed the old behaviour is probably preferable, as we do make use of empty properties quite regularly. |