Red Hat Bugzilla – Bug 468236
Remove Attempted yum / yum-rhn-plugin / pirut Upgrade In Kickstart Post Scripts
Last modified: 2011-08-05 07:57:33 EDT
Description of problem:
Spacewalk renders kickstart files with a %post script which attempts to upgrade some core components. If the kickstart is found to be RHEL 5 (also CentOS 5) the script attempts an upgrade of yum-rhn-plugin, yum, and pirut by fetching the latest version of the package available with wget and attempting an rpm -F. (freshen)
In the case of RHEL 5.0 kickstarts, this attempts to grab the latest RHEL 5.2 versions of these packages which are now coming with different dependencies. Not only will we need to continue adding new dependencies as RHEL progresses, but now yum required new packages completely as dependencies which will not be installed when attempting an rpm freshen. We could change this to an upgrade/install, but we're already counting on *not* installing packages that weren't installed before. (i.e. pirut)
In short, this is an unsustainable approach, we cannot do yum's job, without yum, in a kickstart post script.
NOTE: This issue has limited relevance to Spacewalk, just creating this ticket to track the removal of these lines which attempt to upgrade yum.
Steps to Reproduce:
1. Create a RHEL 5 or CentOS 5 kickstart profile.
2. View kickstart file contents in the UI.
Note the wget of yum-rhn-plugin, yum, pirut, etc.
We should not attempt to manually upgrade packages in kickstart post.
Mass-moving to space13.
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.
Aligning under space16.
We haven't seen progress with this requestion, nor a proposed patch. I gather the current behaviour does not cause big troubles after all.
Closing, please reopen if there is a patch available addressing this issue.