CentOS 6 rebase

[scott]

CentOS released kernel-2.6.32-696.23.1 on March 14th.

I am still showing Kernelcare using 2.6.32-696.20.1.

Are there plans to rebase Kernelcare to 2.6.32-696.23.1? Thats typically what happens. It doesnt look like the patches applied to the upstream 2.6.32-696.23.1 kernel have been applied with Kernelcare. Granted, the changes dont appear to be very vital:

https://access.redhat.com/errata/RHSA-2018:0512

But typically I prefer to see the Kernelcare kernel being used being up to date with what upstream is using.

I thought this mightve been an oversight.

[apb]

Scott,

Please, find the updated reply below

[scott]

Not really an issue of whether or not Kernelcare support the kernel.

Its a question of "why isnt kcarectl --uname reporting the kernel version as being 2.6.32-696.23.1?"

# uname -r

2.6.32-696.18.7.el6.x86_64

# kcarectl --uname

2.6.32-696.20.1.el6

# kcarectl --check

The latest patch is applied.

# kcarectl --update

Kernel is safe

# kcarectl --uname

2.6.32-696.20.1.el6

# kcarectl --check

The latest patch is applied.

# kcarectl --patch-info | head -n 5

OS: centos6

kernel: kernel-2.6.32-696.18.7.el6

time: 2018-03-08 16:53:50

Again...

The latest version of the CentOS 6 kernel is 2.6.32-696.23.1.

As you can see in this example, the underlying kernel being run on this server is 2.6.32-696.18.7 - because I havent rebooted in quite a while.

kcarectl --uname is reporting the kernel version as being 2.6.32-696.20.1 why isnt this reporting 2.6.32-696.23.1?

CentOS released the 2.6.32-696.23.1 kernel on March 14th, 2018. According to the patch-info from Kernelcare, the kernel that Kernelcare is running was last updated on 2018-03-08 16:53:50.

Now to be clear, Im not really having any issues. I dont think the 2.6.32-696.23.1 kernel that CentOS released really fixes anything major. And rebasing the Kernelcare kernels to their upstream equivalents isnt something your team necessarily has to do - but it is something that your team typically does.

Im just wondering if this was an oversight. Its March 27th now, its been nearly two weeks since CentOS released the 2.6.32-696.23.1 kernel. Thats what makes me think that this may be something that slipped through the cracks.

[apb]

Scott,

Ive got an update from KernelCare developers that the latest patch set contains all security fixes to make the kernel to be patched to the level of v.2.6.32-696.23.1. However, kcarectl --uname still shows the previous kernel version (2.6.32-696.20.1) because we have some difficulties with kernel version displaying. Please note, that this is only displaying issue, it will be fixed shortly as our developers are working on it at this moment.