Hide Forgot
Description of problem: I am using a certain number of third-party repositories (i.e. local repositories, RepoForge / DAG etc.) in addition to the RHN-provided channels. To protect the base packages from being replaced I have installed yum-plugin-priorities and assigned priorities to all of the extra repositories. However, I also need a way to assign highest priority to the RHN repos to prevent Red Hat packages from being replaced shall a conflict occur. There is a solution mentioned here: https://bugzilla.redhat.com/show_bug.cgi?id=515720 , that is to assign the priority in the [main] stanza of yum-rhn-plugin configuration file: > /etc/yum/pluginconf.d/rhnplugin.conf: > > [main] > priority = 10 while all the other repositories should be assigned a priority number higher than 10. This, however, has no effect. If I enumerate all channels manually and assign priorities this way: > /etc/yum/pluginconf.d/rhnplugin.conf: > > [rhel-x86_64-server-6] > priority = 10 > > [rhel-x86_64-server-optional-6] > priority = 10 it works perfectly! Unfortunately, this solution is error prone and requires additional administrative load upon changes in system subscriptions. Therefore, I'd like to be able to assign a default priority for all RHN-supplied channels. Version-Release number of selected component (if applicable): yum-rhn-plugin-0.9.1-26.el6_1.1.noarch yum-plugin-priorities-1.1.30-6.el6.noarch yum-3.2.29-17.el6.noarch How reproducible: Add third-party repositories with packages replacing base packages, set up priorities as described and perform # yum clean all # yum -v update Actual results: Third party packages are taking over RHN-supplied packages, unless priorities are specified for every virtual RHN-provided repository, even if a default priority has been specified to be higher than the rest of the repositories. Expected results: All RHN packages always to take over if a higher default priority has been specified in /etc/yum/pluginconf.d/rhnplugin.conf.
The issue has been fixed in spacewalk master by commit 0194651deb2c2d96031a346dab7cfacc0abd00dd 725496 - respect default plugin settings from [main]
Backported to satellite CLIENT-RHEL-6 as commit 9df21cf5ec669f3f35f730c7a5c7923884bfbd7a fixed package exclusion commit bd0acdf0ad1c676cbb8ee4e1aa7d96a60c04c3b2 gpgcheck already is processed by pluginOptions and repoOptions commit fd99878af57b20fe97fc480746e30eda1a415c02 725496 - respect default plugin settings from [main] commit 52a43b2fd3c25e2abd85bbf5e25605578f619761 removed redundant variables
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: yum-rhn-plugin ignored settings from [main] section of rhnplugin.conf except for gpgcheck and enabled. After the fix it takes care of both [main] section settings and per channel settings.
Changing to Verified: With a new package set, the priority parameter in the [main] section is taken in account and packages are downloaded from prioritized repozitories. The priority setting in the [main] section might be still overridden by settings per channel. Verified against: yum-rhn-plugin-0.9.1-35.el6.noarch
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,3 +1 @@ -yum-rhn-plugin ignored settings from [main] section of rhnplugin.conf except for gpgcheck and enabled. +When processing the /etc/yum/pluginconf.d/rhnplugin.conf file, the previous version of rhnplugin incorrectly ignored options in the [main] section other than "enabled" and "gpgcheck". This update ensures that this file is now processed correctly.- -After the fix it takes care of both [main] section settings and per channel settings.
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-2011-1664.html