microcode_ctl and inux-firmware update without kernel

[alik.ross]

Hello,

with upcp "yum update" did run yesterday and ( microcode_ctl-2:2.1-22.el7.x86_64 & linux-firmware-20170606-56.gitc990aae.el7.noarch ) updated and now cpanel show reboot server to apply changes.

but kernel does not updated ( i does not enabled beta resp )

is it ok and can i reboot server without kernel update ?

yum update history info for yesterday :

yum history info 75
Loaded plugins: fastestmirror, langpacks, rhnplugin, universal-hooks
This system is receiving updates from CLN.
Transaction ID : 75
Begin time : Thu Jan 4 23:05:41 2018
Begin rpmdb : 2699:3ad3357d2837309768bef43a628d487e0a9b54bd
End time : 23:06:09 2018 (28 seconds)
End rpmdb : 2699:c5c69174249dacbd2f79f4712bd0d9d454e148b3
User : root <root>
Return-Code : Success
Command Line : --assumeyes --config /etc/yum.conf update
Transaction performed with:
Installed rpm-4.11.3-25.el7.x86_64 @cloudlinux-x86_64-server-7
Installed yum-3.4.3-154.el7.cloudlinux.noarch @cloudlinux-x86_64-server-7
Installed yum-metadata-parser-1.1.4-10.el7.x86_64 @anaconda
Installed yum-plugin-fastestmirror-1.1.31-42.el7.noarch @cloudlinux-x86_64-server-7
Installed yum-rhn-plugin-2.0.1-9.el7.cloudlinux.1.noarch @cloudlinux-base
Packages Altered:
Updated iwl100-firmware-39.31.5.1-56.el7.noarch @cloudlinux-x86_64-server-7
Update 39.31.5.1-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl1000-firmware-1:39.31.5.1-56.el7.noarch @cloudlinux-x86_64-server-7
Update 1:39.31.5.1-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl105-firmware-18.168.6.1-56.el7.noarch @cloudlinux-x86_64-server-7
Update 18.168.6.1-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl135-firmware-18.168.6.1-56.el7.noarch @cloudlinux-x86_64-server-7
Update 18.168.6.1-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl2000-firmware-18.168.6.1-56.el7.noarch @cloudlinux-x86_64-server-7
Update 18.168.6.1-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl2030-firmware-18.168.6.1-56.el7.noarch @cloudlinux-x86_64-server-7
Update 18.168.6.1-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl3160-firmware-22.0.7.0-56.el7.noarch @cloudlinux-x86_64-server-7
Update 22.0.7.0-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl3945-firmware-15.32.2.9-56.el7.noarch @cloudlinux-x86_64-server-7
Update 15.32.2.9-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl4965-firmware-228.61.2.24-56.el7.noarch @cloudlinux-x86_64-server-7
Update 228.61.2.24-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl5000-firmware-8.83.5.1_1-56.el7.noarch @cloudlinux-x86_64-server-7
Update 8.83.5.1_1-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl5150-firmware-8.24.2.2-56.el7.noarch @cloudlinux-x86_64-server-7
Update 8.24.2.2-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl6000-firmware-9.221.4.1-56.el7.noarch @cloudlinux-x86_64-server-7
Update 9.221.4.1-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl6000g2a-firmware-17.168.5.3-56.el7.noarch @cloudlinux-x86_64-server-7
Update 17.168.5.3-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl6000g2b-firmware-17.168.5.2-56.el7.noarch @cloudlinux-x86_64-server-7
Update 17.168.5.2-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl6050-firmware-41.28.5.1-56.el7.noarch @cloudlinux-x86_64-server-7
Update 41.28.5.1-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl7260-firmware-22.0.7.0-56.el7.noarch @cloudlinux-x86_64-server-7
Update 22.0.7.0-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated iwl7265-firmware-22.0.7.0-56.el7.noarch @cloudlinux-x86_64-server-7
Update 22.0.7.0-57.el7_4.noarch @cloudlinux-x86_64-server-7
Updated linux-firmware-20170606-56.gitc990aae.el7.noarch @cloudlinux-x86_64-server-7
Update 20170606-57.gitc990aae.el7_4.noarch @cloudlinux-x86_64-server-7
Updated microcode_ctl-2:2.1-22.el7.x86_64 @cloudlinux-x86_64-server-7
Update 2:2.1-22.2.el7.x86_64 @cloudlinux-x86_64-server-7
history info

[apb]

I suggest the kernel be also upgraded before rebooting the system (to protect against Meltdown vulnerability) by running:

# yum clean all --enablerepo=cloudlinux-updates-testing && yum update linux-firmware microcode_ctl && yum install kernel-3.10.0-714.10.2.lve1.4.79.el7 --enablerepo=cloudlinux-updates-testing

[apb]

> I suggest the kernel be also upgraded before rebooting the system (to protect against Meltdown vulnerability) by running:
>
> # yum clean all --enablerepo=cloudlinux-updates-testing && yum update linux-firmware microcode_ctl && yum install kernel-3.10.0-714.10.2.lve1.4.79.el7 --enablerepo=cloudlinux-updates-testing

I want update kernel after stable version released. Is it ok ?

[apb]

CloudLinux OS 7 and 6 Hybrid kernels are already in the stable branch.
The upgrade instructions can be found at: https://cloudlinux.com/cloudlinux-os...and-cloudlinux

[apb]

CloudLinux OS 7 and 6 Hybrid kernels are already in the stable branch. The upgrade instructions can be found at: https://cloudlinux.com/cloudlinux-os...and-cloudlinux

[lyndaw.atson19798]

> CloudLinux OS 7 and 6 Hybrid kernels are already in the stable branch.
> The upgrade instructions can be found at: https://cloudlinux.com/cloudlinux-os...nd-cloudlinux/
>
> Exactly what I needed! You just saved me several hours. Thanks!

[skhristich]

> Exactly what I needed! You just saved me several hours. Thanks!

Hello,
Thanks for the feedback, nice to hear that!