| Summary: | new configuration for rhsm.manage_repos should be exposed | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | John Sefler <jsefler> |
| Component: | subscription-manager | Assignee: | Bryan Kearney <bkearney> |
| Status: | CLOSED ERRATA | QA Contact: | Entitlement Bugs <entitlement-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3 | CC: | dgoodwin, skallesh, spandey |
| 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-06-20 13:06: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: | |
| Bug Depends On: | |||
| Bug Blocks: | 738066 | ||
|
Description
John Sefler
2012-02-27 18:31:19 UTC
Fixed in subscription-manager.git: 2cca158971efdfce9621a1de61b0874907357d56 You should now see manage_repos = 1 in the [rhsm] section of a fresh RPM installation of subscription-manager. Moving the bug to verified. RPM used: [root@dhcp201-162 ~]# rpm -qa | grep subscription-manager subscription-manager-0.99.8-1.git.16.f7ed3d6.el6.x86_64 subscription-manager-migration-0.99.8-1.git.16.f7ed3d6.el6.x86_64 subscription-manager-firstboot-0.99.8-1.git.16.f7ed3d6.el6.x86_64 subscription-manager-migration-data-1.12.1-1.git.4.7b6cf92.el6.noarch subscription-manager-gnome-0.99.8-1.git.16.f7ed3d6.el6.x86_64 subscription-manager-debuginfo-0.99.8-1.el6.x86_64 [root@dhcp201-162 ~]# subscription-manager config --rhsm.manage_repos=0 [root@dhcp201-162 ~]# cat /etc/rhsm/rhsm.conf | grep manage_repo manage_repos = 0 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0804.html |