Red Hat Bugzilla – Bug 466831
pkgSkipList is not being honored for automatic updates from RHN
Last modified: 2010-10-26 07:47:09 EDT
Description of problem:
On a RHEL 4.7 box, with up2date-4.7.1-17.el4, the pkgSkipList is not being honored when automatic updates are applied via RHN. The pkgSkipList from /etc/sysconfig/rhn/up2date has:
Yet every time an updated release of java-1.5.0-ibm is available, it's automatically applied via our RHN subscription. This breaks an application
that we have running on the system, and causes unplanned down-time.
We have our own Satellite server, if that matters. We're running Satellite 4.2.3.
The first time this happened, we thought that perhaps it was because we had
not restarted rhnsd when the pkgSkipList was modified (via editing the file
directly). However, we've restarted rhnsd several times since then, and the
last two java-1.5.0-ibm updates have still been applied.
Version-Release number of selected component (if applicable):
It has happened the last three times Red Hat has released an updated version of
java-1.5.0-ibm and java-1.5.0-ibm-devel, so it can be reproduced.
Steps to Reproduce:
1. Red Hat releases an updated java-1.5.0-ibm release (like 18.104.22.168)
2. just wait, it will be installed despite the pkgSkipList
java-1.5.0-ibm and java-1.5.0-ibm-devel still get automatically updated,
despite the contents of the pkgSkipList
They should be skipped.
I've checked and tested the behavior of up2date in both RHEL-4.7 and
RHEL-4.8 and the pkgSkipList feature works correctly: the packages listed
are being skipped during automatic errata update scheduler by Satellite.
The only way you can achieve the behavior described in the initial comment
(i.e. pkgSkipList directive is being ignored during automatic errata update)
is when you set forceInstall directive in /etc/sysconfig/rhn/up2date to Yes
(it's configurable via up2date-config utility for example).
forceInstall[comment]=Force package installation, ignoring package, file and
config file skip list
If you believe this is not the case, please raise your concern. Otherwise
I'm inclined to close this bug report with resolution 'worksforme'.
We also believe that this issue was fixed some time several months ago, as we noticed the problem seemed to stop at some point, so I'm fine with this issue being closed.
I can, however, guarantee that it was not working when I reported this bug. forceInstall is set to 0 and has never been modified.
Thank you for this feedback.
I have no reason to question the validity of the opening report, though
I'm currently unable to reproduce the problem.
If the problem reappears, please feel free to reopen this bug.
Closing with 'worskforme' for now.