Dear All,
Scientific Linux pushed a new SL3 yum-conf package 14 Dec, to
point sl-errata to SL3.0.9. It overwrote /etc/yum.conf (it saved previous
as yum.conf.rpmsave).
We use a modified SL3 /etc/yum.conf to include repos for glite updates.
So, I retrofitted the new yum.conf with our glite mods.
All our production glite nodes previously had all pending glite updates.
But a test glite machine, that had pending glite updates, then
auto-updated itself with all pending glite updates in the wee hours, as if
yum -y update was done in nightly yum cron.
I believe this is due to new yum-conf - whereas the previous
/etc/cron.daily/yum.cron used to explicitly only update from the
[sl-errata] stanza in /etc/yum.conf, the new version puts
exclude=kernel* openafs* GFS*
under [main] in a /tmp copy of /etc/yum.conf & does yum -y update using
that file. So all pending updates (except kernel* openafs* gfs* ) are
applied.
Did this happen to anyone else?
It's said to be dangerous to auto-apply glite updates, particularly since
some of them require by-hand tweaks, site-info.def changes, etc.
One solution might be to revert to earlier yum.cron that only updates
[sl-errata], or turn off yum cron.
Observations &/or advice welcome.
|