The effect of installing SL_yum-cron_no_automated_apply_updates and SL_yum-cron_no_default_excludes were *both* undone by the update. As Bill implies, the TUV change of a config file back to the default for the sake of a few comment lines seems a bit severe (although, admittedly, those comment lines are important.)
rpmconf(8) is your friend. I run this after every operating system update to production servers (and most especially point releases.) It finds and helps you resolve these kinds of issues. It is available in EPEL. Should the SL packages rerun their postinstall scriptlets (via, say, a %triggerin) when a new yum-cron package comes along? Or is this a bug for TUV? Tim Kanuka Canadian Light Source Inc. -----Original Message----- From: owner-scientific-linux-us...@listserv.fnal.gov [mailto:owner-scientific-linux-us...@listserv.fnal.gov] On Behalf Of Bill Maidment Sent: February 5, 2016 23:28 To: Bill Maidment <b...@maidment.me>; scientific-linux-us...@fnal.gov Subject: RE: Upgrading SL 7.1 to SL 7.2 - auto update switched back on That should have been /etc/yum/yum-cron.conf -----Original message----- > From:Bill Maidment <b...@maidment.me> > Sent: Saturday 6th February 2016 16:21 > To: scientific-linux-us...@fnal.gov > Subject: Upgrading SL 7.1 to SL 7.2 - auto update switched back on > > Be aware > The upgrade overwrites /etc/yum/yum.conf (putting the old file in > /etc/yum/yum.conf.saved). > All for the sake of a few changed comment lines. > > Cheers > Bill Maidment > >
