Bug 591508
Summary: | disabled sm yum plugin displays repo for subscribed product | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | spandey |
Component: | subscription-manager | Assignee: | Jeff Ortel <jortel> |
Status: | CLOSED NOTABUG | QA Contact: | wes hayutin <whayutin> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 6.1 | CC: | alikins, bkearney, ckannan, kbanerje, shaines, spandey, syeghiay, whayutin |
Target Milestone: | rc | Keywords: | QA-Closed |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-10-03 00:56:55 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: | 568421, 636830 |
Description
spandey
2010-05-12 12:50:27 UTC
Please verify both in on premises and hosted. I think this is as designed for the plugin. Reassigning to the client folk so they can comment more. This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. It has been denied for the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. ** raising priority, recreated this morning Looks like we create the repo files when the rhsmplugin is enabled. Then if we disable it, it doesn't run and can not remove the repo files. It should be able to add those repo's dynamically without creating the repo files [1]. We would probably need to cache the repo data somewhere if we don't want to have to generate it from the certs everytime. skvidal seems to indicate this is doable. [1] though, it is nice to have actual repo files for every repo, just from a sanity standpoint. This works as designed! The rhsmplugin is *not* the rhnplugin and should not be expected to behave like it. The plugin is for synchronizing the .repo file with entitlement certificates. So, if you want to disable the redhat repos, edit the .repo file (enabled=0) after you've disabled the rhsmplugin. Or, IIRC, you can disable in PackageKit. Managing an actual repo file provides greater flexibility for system admins and is a more "yum-like" approach. Changing rhsmplugin to dynamically load the repos (like rhnplugin) would be a big regression, IHMO. jeff.. one question before I close this out... If I susbcribe via rhsm, and the content set is set to enabled. If I disable it manually via direct editing of the /etc/yum/[REPO FILE] will the plugin respect my change? Said another way, is the enabled bit a default? Short answer is yes. The rhsm backend (repolib) defines properties in the .repo file that it manages as mutable (or not). Mutable properties are allowed to be manually edited. That is, if you edit the .repo file, rhsm will respect your changes. Non-mutable properties (such as baseurl) are strictly managed by rhsm and outside changes are not respected. They are corrected as needed when repolib does it's merge. Other properties (those not known to rhsm) are also left unchanged. So, you can add extra properties to a repo defined in the .repo file and rhsm will also leave those alone. The rhsm backend was designed to work in harmony with system administrators who might want to exit the .repo file. Or, other applications such as PackageKit. Per this dicussion, I am closing as not a bug. |