Bug 1319927
Summary: | [RFE] subscription-manager should automatically enable yum plugins | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | William <wlehman> |
Component: | subscription-manager | Assignee: | Jiri Hnidek <jhnidek> |
Status: | CLOSED ERRATA | QA Contact: | John Sefler <jsefler> |
Severity: | medium | Docs Contact: | Filip Hanzelka <fhanzelk> |
Priority: | medium | ||
Version: | 7.1 | CC: | bcourt, candlepin-bugs, cdonnell, csnyder, jhnidek, khowell, rjerrido, skallesh, vrjain |
Target Milestone: | rc | Keywords: | FutureFeature, Triaged |
Target Release: | 7.4 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | subscription-manager-1.20.8-1 | Doc Type: | Release Note |
Doc Text: |
*subscription-manager* now automatically enables the `subscription-manager` and `product-id` yum plugins
With this update, the *subscription-manager* utility automatically enables the `yum` plugins: `subscription-manager` and `product-id`. This update benefits users of Red Hat Enterprise Linux who previously used the *rhn-client-tools* utility to register their systems to Red Hat Network Classic or who still use it with Satellite 5 entitlement servers, and who have temporarily disabled the `yum` plugins. As a result, it is easier for users to start using the newer *subscription-manager* tools for entitlements. Note that running *subscription-manager* displays a warning message indicating how to change this default behavior if it is not desirable.
|
Story Points: | --- |
Clone Of: | 1317690 | Environment: | |
Last Closed: | 2018-04-10 09:47:31 UTC | Type: | Bug |
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: | 1420851, 1469152 |
Description
William
2016-03-21 20:46:44 UTC
When setting the release, sub-man should validate that the yum plugin is enabled. There will be no further check after the release has been set. Suggestion: The logic to check if the plugin (read from "/etc/yum/pluginconf.d/subscription-manager.conf") is enabled should be run on subman startup. To be clear this means the warning message should be output on any subman command AND on GUI start up. Verification : Case 1. Verify yum plugins are automatically enabled and user is informed when subscription-manager commands are run on CLI: [root@dhcp35-121 ~]# subscription-manager version server type: Red Hat Subscription Management subscription management server: 2.0.43-1 subscription management rules: 5.26 subscription-manager: 1.20.5-1.el7 Disable the subscription-manager yum plugin: [root@dhcp35-121 ~]# sed -i s/enabled=./enabled=0/g /etc/yum/pluginconf.d/subscription-manager.conf Verify if the plugin is disabled: [root@dhcp35-121 ~]# grep enabled /etc/yum/pluginconf.d/subscription-manager.conf enabled=0 Now execute the sub-man command on CLI and observe the warning message conveying user that the plugin is enabled automatically: [root@dhcp35-121 ~]# subscription-manager register Registering to: subscription.rhsm.stage.redhat.com:443/subscription Username: shwetha_tier1_test Password: The system has been registered with ID: 9f559a08-bb1a-49ca-a060-02cc66eba5c0 The registered system name is: dhcp35-121.lab.eng.blr.redhat.com WARNING The yum plugins: /etc/yum/pluginconf.d/subscription-manager.conf were automatically enabled for the benefit of Red Hat Subscription Management. If not desired, use "subscription-manager config --rhsm.auto_enable_yum_plugins=0" to block this behavior. Verify if the plugin is enabled: [root@dhcp35-121 ~]# grep enabled /etc/yum/pluginconf.d/subscription-manager.conf enabled=1 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. https://access.redhat.com/errata/RHBA-2018:0681 |