The "fix" for below was simply removing the old kernels. But how it got into the bad state ??? Anyway, for those that might see the same bad state. On 11/10/26 12:40 PM, Christopher Cox via AlmaLinux Users wrote:

I went to try and do updates to a VM in our Azure instance that is using Almalinux 10 and got the following:

# dnf update Last metadata expiration check: 0:50:06 ago on Thu 05 Nov 2026 07:26:35 PM UTC. Error:  Problem: package kernel-uki-virt-6.12.0-211.61.1.el10_2.x86_64 from @System requires kernel-modules-core-uname-r = 6.12.0-211.61.1.el10_2.x86_64, but none of the providers can be installed   - conflicting requests (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Now, what is really weird, is I know we've applied updates before, maybe as recently as a week or two ago.  With a reboot afterwards.

# uname -a Linux vm-example-usw2-001 6.12.0-211.47.1.el10_2.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Aug 13 10:40:14 EDT 2026 x86_64 GNU/Linux

Notice the kernel that is running.

# rpm -q -a | grep kernel-6 kernel-6.12.0-211.47.1.el10_2.x86_64 kernel-6.12.0-211.61.1.el10_2.x86_64 kernel-6.12.0-211.68.1.el10_2.x86_64

And from dmesg:

dmesg | grep vmlinuz [    0.000000] Command line: BOOT_IMAGE=(hd0,gpt3)/ vmlinuz-6.12.0-211.47.1.el10_2.x86_64 root=UUID=472965f2-0739-4ac0- b75a-710112ce4699 ro loglevel=3 console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 no_timer_check nvme_core.io_timeout=240 biosdevname=0 net.ifnames=0 [    0.027509] Kernel command line: BOOT_IMAGE=(hd0,gpt3)/ vmlinuz-6.12.0-211.47.1.el10_2.x86_64 root=UUID=472965f2-0739-4ac0- b75a-710112ce4699 ro loglevel=3 console=tty1 console=ttyS0 earlyprintk=ttyS0 rootdelay=300 no_timer_check nvme_core.io_timeout=240 biosdevname=0 net.ifnames=0 [    0.027673] Unknown kernel command line parameters "BOOT_IMAGE=(hd0,gpt3)/ vmlinuz-6.12.0-211.47.1.el10_2.x86_64 biosdevname=0", will be passed to user space. [    1.134115]     BOOT_IMAGE=(hd0,gpt3)/vmlinuz-6.12.0-211.47.1.el10_2.x86_64

So, there's are really two problems.  One, I can't do updates anymore because the first issue, but the second issue is why after doing updates am I still on an old kernel (???)  I have done nothing configuration wise outside of the defaults in that regard.  I'm stumped.  Suggestions?

I'm thinking (guessing) it has to do with how boot is actually done for this in the cloud on Azure.

_______________________________________________ AlmaLinux Users mailing list -- users@lists.almalinux.org To unsubscribe send an email to users-leave@lists.almalinux.org