Automatic upgrading from SL6.4 to SL6.5

Support
1

Hello all,

Recently I was surprised to see that a Puppet/Foreman installed server
with operating system SL6.4 would immediately switch to SL6.5.

I do not know if some people got bitten by the same thing but it took
me some time to realize that this was the consequence because of
yum-conf-sl6x being installed by default on SL6.4 [1] and the
availability of SL6.5.

As I prefer to manage myself the version of SL used on production
servers, I looked for a way to prevent this and I chose to hack the
Kickstart file :

[…]
%packages --excludedocs --nobase
ntp
wget
@Core
-yum-conf-sl6x
[…]

I do not know if there is a better way. Am I the only one to experience
this issue ?

Thanks

JM

··· -- ------------------------------------------------------------------------ Jean-michel BARBET | Tel: +33 (0)2 51 85 84 86 Laboratoire SUBATECH Nantes France | Fax: +33 (0)2 51 85 84 79 CNRS-IN2P3/Ecole des Mines/Universite | E-Mail: barbet@subatech.in2p3.fr ------------------------------------------------------------------------
2

You will also want to remove yum-autoupdate. It was auto updating my hosts , much to my surprise. I haven't updated my SL hosts to 6.5 but <6.5 this package was installed even in a minimal install. I wrote http://forge.puppetlabs.com/treydock/yum_cron to handle disable/removal of that package in favor of more configurable yum-cron.

  • Trey