CentOS - Aug 2020 - 8.2.2004 Latest yum update renders machine unbootable

On 8/1/20 5:00 AM, Johnny Hughes wrote:
>
> I would wait and install everything as a group. We should have 
> something soon. 
First off, Johnny and all of the rest of the CentOS team, thank you for 
your efforts!

Second, to all with this problem, I too experienced the issue (I posted 
on the CentOS-Devel list my findings).? To those who seem to think more 
testing could have prevented the issue, let me just say that while the 
FIRST update to the new shim-x64, grub2, and kernel stack failed for me 
(and that update was done with the GUI updater that reboots for the 
actual update), I WAS able to recover using the install media's rescue 
mode tools as documented in my posts on CentOS-devel.? I'm glad to 
provide any and all logs of the processes I did, but the short of it is 
that after I successfully downgraded grub2 it still wouldn't boot, but I 
was able to do a reinstall of grub2 (81, the older version) to get it to 
boot with the old grub2, the new shim-x64, and the new kernel, and then 
I was able to successfully update grub2 with dnf on a command line.? So 
I have the following installed:
[lowen at localhost ~]$ rpm -q shim-x64
shim-x64-15-13.el8.x86_64
[lowen at localhost ~]$ rpm -qa | grep ^grub2
grub2-common-2.02-87.el8_2.noarch
grub2-tools-2.02-87.el8_2.x86_64
grub2-efi-x64-2.02-87.el8_2.x86_64
grub2-tools-extra-2.02-87.el8_2.x86_64
grub2-pc-2.02-87.el8_2.x86_64
grub2-tools-efi-2.02-87.el8_2.x86_64
grub2-tools-minimal-2.02-87.el8_2.x86_64
grub2-pc-modules-2.02-87.el8_2.noarch
grub2-efi-x64-modules-2.02-87.el8_2.noarch
[lowen at localhost ~]$ rpm -qa | grep ^kernel|grep 147
kernel-devel-4.18.0-147.8.1.el8_1.x86_64
kernel-4.18.0-147.8.1.el8_1.x86_64
kernel-modules-4.18.0-147.8.1.el8_1.x86_64
kernel-core-4.18.0-147.8.1.el8_1.x86_64
[lowen at localhost ~]$

And this is on a machine that previously crashed during boot with the 
exactly the same packages.? So even on the same hardware the same update 
(done a bit differently) had different results.

It's quite possible, based on my experience with this particular issue, 
that if I had the whole system rolled back to where it was before the 
GUI update and if I then updated it again that it could just simply work 
ok afterwards.? It's very hard to test for intermittent issues!

On 8/1/20 11:02 AM, Lamar Owen wrote:
> ...
> [lowen at localhost ~]$ rpm -qa | grep ^kernel|grep 147
> kernel-devel-4.18.0-147.8.1.el8_1.x86_64
> kernel-4.18.0-147.8.1.el8_1.x86_64
> kernel-modules-4.18.0-147.8.1.el8_1.x86_64
> kernel-core-4.18.0-147.8.1.el8_1.x86_64
> [lowen at localhost ~]$ 
Well, I sure fat-fingered that command.... let's try it again:

[lowen at localhost ~]$ rpm -qa | grep ^kernel|grep 193.14
kernel-headers-4.18.0-193.14.2.el8_2.x86_64
kernel-devel-4.18.0-193.14.2.el8_2.x86_64
kernel-modules-4.18.0-193.14.2.el8_2.x86_64
kernel-tools-4.18.0-193.14.2.el8_2.x86_64
kernel-core-4.18.0-193.14.2.el8_2.x86_64
kernel-tools-libs-4.18.0-193.14.2.el8_2.x86_64
kernel-4.18.0-193.14.2.el8_2.x86_64
[lowen at localhost ~]$ uname -a
Linux localhost.localdomain 4.18.0-193.14.2.el8_2.x86_64 #1 SMP Sun Jul 
26 03:54:29 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
[lowen at localhost ~]$

On Sat, Aug 1, 2020 at 8:58 PM Lamar Owen <lowen at pari.edu> wrote:
> On 8/1/20 11:02 AM, Lamar Owen wrote:
> > ...
> > [lowen at localhost ~]$ rpm -qa | grep ^kernel|grep 147
> > kernel-devel-4.18.0-147.8.1.el8_1.x86_64
> > kernel-4.18.0-147.8.1.el8_1.x86_64
> > kernel-modules-4.18.0-147.8.1.el8_1.x86_64
> > kernel-core-4.18.0-147.8.1.el8_1.x86_64
> > [lowen at localhost ~]$
>
> Well, I sure fat-fingered that command.... let's try it again:
>
> [lowen at localhost ~]$ rpm -qa | grep ^kernel|grep 193.14
> kernel-headers-4.18.0-193.14.2.el8_2.x86_64
> kernel-devel-4.18.0-193.14.2.el8_2.x86_64
> kernel-modules-4.18.0-193.14.2.el8_2.x86_64
> kernel-tools-4.18.0-193.14.2.el8_2.x86_64
> kernel-core-4.18.0-193.14.2.el8_2.x86_64
> kernel-tools-libs-4.18.0-193.14.2.el8_2.x86_64
> kernel-4.18.0-193.14.2.el8_2.x86_64
> [lowen at localhost ~]$ uname -a
> Linux localhost.localdomain 4.18.0-193.14.2.el8_2.x86_64 #1 SMP Sun Jul
> 26 03:54:29 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
> [lowen at localhost ~]$
>
>
>
> RedHat fixes.
https://access.redhat.com/errata/RHBA-2020:3265
https://access.redhat.com/errata/RHBA-2020:3262

--
Lee

I got 5 CentOS 8.1 VMs minimal  install.
When I did the update I got 1 that had dnf issues and corrupted rpm DB and
another 1  that didn't boot.
Restore from snapshot and again update -> no issues. For me it looks more
like a random issue.

Best Regards,
Strahil Nikolov

?? 1 ?????? 2020 ?. 18:28:09 GMT+03:00, Lamar Owen <lowen at pari.edu>
??????:
>On 8/1/20 11:02 AM, Lamar Owen wrote:
>> ...
>> [lowen at localhost ~]$ rpm -qa | grep ^kernel|grep 147
>> kernel-devel-4.18.0-147.8.1.el8_1.x86_64
>> kernel-4.18.0-147.8.1.el8_1.x86_64
>> kernel-modules-4.18.0-147.8.1.el8_1.x86_64
>> kernel-core-4.18.0-147.8.1.el8_1.x86_64
>> [lowen at localhost ~]$ 
>
>Well, I sure fat-fingered that command.... let's try it again:
>
>[lowen at localhost ~]$ rpm -qa | grep ^kernel|grep 193.14
>kernel-headers-4.18.0-193.14.2.el8_2.x86_64
>kernel-devel-4.18.0-193.14.2.el8_2.x86_64
>kernel-modules-4.18.0-193.14.2.el8_2.x86_64
>kernel-tools-4.18.0-193.14.2.el8_2.x86_64
>kernel-core-4.18.0-193.14.2.el8_2.x86_64
>kernel-tools-libs-4.18.0-193.14.2.el8_2.x86_64
>kernel-4.18.0-193.14.2.el8_2.x86_64
>[lowen at localhost ~]$ uname -a
>Linux localhost.localdomain 4.18.0-193.14.2.el8_2.x86_64 #1 SMP Sun Jul
>
>26 03:54:29 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
>[lowen at localhost ~]$
>
>
>_______________________________________________
>CentOS mailing list
>CentOS at centos.org
>https://lists.centos.org/mailman/listinfo/centos