[CentOS-devel] CentOS-7 Public QA Buildtag 140617

On 06/25/2014 11:09 PM, Fred Smith wrote:
> On Wed, Jun 25, 2014 at 03:48:31PM -0600, Scott Dowdle wrote:
>> Greetings,
>>
>> ----- Original Message -----
>>> # yum reinstall kernel
>>> Loaded plugins: langpacks
>>> Skipping the running kernel: kernel-3.10.0-123.el7.x86_64
>>> Error: Nothing to do
>>
>> The issue is the kernel you are running/have installed is newer than
>> the one provided by the "yum distro-sync full" operation and updating to
>> older kernels isn't something it was designed to do.  You can get past
>> that by manually installing the older kernel by referring to it by the
>> complete name including version number... and then rebooting making sure
>> to boot the older kernel.  When the undesired kernel is no longer the
>> one that is running, you can remove it... and a "yum distro-sync full"
>> should be happy.
> 
> So, if I'm using a kernel I got from the 7-RC (the -latest) "repo",
> how could it have gotten out of sync?
> 
> Looking at "yum list available" to see what kernel is on the "repo",
> I see it's 3.10.0-123 which is the same as what's installed.
> 
> Seems like a "catch-22" wherein if you have only one kernel on the
> box, you can't replace it because it's the only kernel on the box.
> or something of that ilk.
> 

yum wont replace the kernel you are currently running, that is indeed an
issue and the reason you hit this is that the new kernel in the latest
build from today is indeed different and has different code inside there
- but its the same name-version-release

you just hit a classic CentOS QA issue - and this is also why we go out
of our way to be pedantic about not-for-users.

your only way to get the new kernel is to reinstall the machine, or to
find something else somewhere ( plus kernel ? ) boot it, replace the
distro kernel, boot back and hope for the best.



-- 
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc