The sl-release rpm is supposed to fix that as part of the %post scripts.
Alas, it appears there is yet-another-bug there.... Pat On 09/14/2018 09:42 AM, Alec Habig wrote:
Patrick Riehecky writes:Can I see the output of : cat /etc/yum/vars/slreleaseverAhh, that could be it: "7.4". I did an upgrade-in-place, installing sl-release-7.5-2.sl7.x86_64, cleaning the yum cache, and updating. That apparently didn't update this file. That file (which is owned by the sl-release package) did not update the number. Interestingly, $ rpm --verify sl-release shows no changes to the files. $ cat /etc/redhat-release Scientific Linux release 7.5 (Nitrogen) does what you'd expect. Checking on some other machines that were originally installed as 7.3 and upgraded in place twice, they're at 7.3 also. Manually changing /etc/yum/vars/slreleasever to 7.5 gets me loads of updates, including the freeipmi. So: short summary: upgrading sl-release does change TUV's release tag, but not the SL release tag file, and does not notice that fact on a verify. The procedure which served me well for many 6.x upgrades needs one more tweak for 7.x upgrades! Is this expected behavior, or is there somethign to be tweaked with the sl-release rpm (or its scripts)? thanks! Alec
-- Pat Riehecky Fermi National Accelerator Laboratory www.fnal.gov www.scientificlinux.org
