Problems with the microcode_ctl package in the registry.redhat.io/rhel9/rhel-bootc:9.4 image

[tux1980]

Hi Team,

in general the demo is structured absolutely great! Unfortunately in All Containerfiles I fail with the container Image: registry.redhat.io/rhel9/rhel-bootc:9.4 Some problems with the microcode_ctl package.

Always the same error - maybe you can help us out here?

Upgrading        : microcode_ctl-4:20230808-2.20240531.1.el9_4.noarch    7/14 
  Running scriptlet: microcode_ctl-4:20230808-2.20240531.1.el9_4.noarch    7/14 
  Cleanup          : glibc-2.34-100.el9_4.3.x86_64                         8/14 
  Cleanup          : glibc-minimal-langpack-2.34-100.el9_4.3.x86_64        9/14 
  Cleanup          : linux-firmware-20240716-143.2.el9_4.noarch           10/14 
  Cleanup          : linux-firmware-whence-20240716-143.2.el9_4.noarch    11/14 
  Running scriptlet: microcode_ctl-4:20230808-2.20231009.1.el9_3.noarch   12/14 
/var/tmp/rpm-tmp.tMeQmm: line 11: /var/lib/rpm-state/microcode_ctl_un_intel-ucode: No such file or directory
/var/tmp/rpm-tmp.tMeQmm: line 13: /var/lib/rpm-state/microcode_ctl_un_ucode_caveats: No such file or directory
/var/tmp/rpm-tmp.tMeQmm: line 15: /var/lib/rpm-state/microcode_ctl_un_file_list: No such file or directory
error: %preun(microcode_ctl-4:20230808-2.20231009.1.el9_3.noarch) scriptlet failed, exit status 1

Error in PREUN scriptlet in rpm package microcode_ctl
  Cleanup          : glibc-gconv-extra-2.34-100.el9_4.3.x86_64            13/14 
error: microcode_ctl-4:20230808-2.20231009.1.el9_3.noarch: erase failed

  Running scriptlet: glibc-gconv-extra-2.34-100.el9_4.3.x86_64            13/14 
  Cleanup          : glibc-common-2.34-100.el9_4.3.x86_64                 14/14 
  Running scriptlet: microcode_ctl-4:20230808-2.20240531.1.el9_4.noarch   14/14 
  Running scriptlet: glibc-common-2.34-100.el9_4.3.x86_64                 14/14 
  Verifying        : glibc-2.34-100.el9_4.4.x86_64                         1/14 
  Verifying        : glibc-2.34-100.el9_4.3.x86_64                         2/14 
  Verifying        : glibc-common-2.34-100.el9_4.4.x86_64                  3/14 
  Verifying        : glibc-common-2.34-100.el9_4.3.x86_64                  4/14 
  Verifying        : glibc-gconv-extra-2.34-100.el9_4.4.x86_64             5/14 
  Verifying        : glibc-gconv-extra-2.34-100.el9_4.3.x86_64             6/14 
  Verifying        : glibc-minimal-langpack-2.34-100.el9_4.4.x86_64        7/14 
  Verifying        : glibc-minimal-langpack-2.34-100.el9_4.3.x86_64        8/14 
  Verifying        : linux-firmware-20240905-143.3.el9_4.noarch            9/14 
  Verifying        : linux-firmware-20240716-143.2.el9_4.noarch           10/14 
  Verifying        : linux-firmware-whence-20240905-143.3.el9_4.noarch    11/14 
  Verifying        : linux-firmware-whence-20240716-143.2.el9_4.noarch    12/14 
  Verifying        : microcode_ctl-4:20230808-2.20240531.1.el9_4.noarch   13/14 
  Verifying        : microcode_ctl-4:20230808-2.20231009.1.el9_3.noarch   14/14 
Installed products updated.
Error: Transaction failed

Upgraded:
  glibc-2.34-100.el9_4.4.x86_64                                                 
  glibc-common-2.34-100.el9_4.4.x86_64                                          
  glibc-gconv-extra-2.34-100.el9_4.4.x86_64                                     
  glibc-minimal-langpack-2.34-100.el9_4.4.x86_64                                
  linux-firmware-20240905-143.3.el9_4.noarch                                    
  linux-firmware-whence-20240905-143.3.el9_4.noarch                             
  microcode_ctl-4:20230808-2.20240531.1.el9_4.noarch                            
Failed:
  microcode_ctl-4:20230808-2.20231009.1.el9_3.noarch                            

Error: building at STEP "RUN dnf -y update": while running runtime: exit status 1
[root@openshift bootc-container-simple]# 

Thanks Wolfgang

[kubealex]

Hi @tux1980!

Thanks for reporting this, may I please ask you some details about the host you are trying to build the image on? (arch, distro, version, etc.) It will definitely help, I just tried all builds on a fresh RHEL9.4 x86_64 VM and I wasn't able to replicate the issue.

Thank you!

[tux1980]

Hi. Same here, is a Server with RHEL 9.4 - X86. But is not a VM, is a bare metal Installation on my Hetzner Server.

[root@openshift ~]# uname -a
Linux openshift.kimmlingen.local 5.14.0-427.37.1.el9_4.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Sep 13 12:41:50 EDT 2024 x86_64 x86_64 x86_64 GNU/Linux#

[root@openshift ~]# uname -m
x86_64
[root@openshift ~]#

Thanks Wolfgang

[kubealex]

Super weird, I also have a box on Hetzner to do this. May I ask you to run a test removing the image and running the build from scratch?

podman rmi registry.redhat.io/rhel9/rhel-bootc:9.4

Thanks, Ale

[tux1980]

Hi Ale, thanks for putting up with me:). And.... yes after built it again from scratch. it works now. At least with the simple one - but then it should also works with all the upcoming excersices. Perfect.

[tux1980]

Ok, the container starts, bit I cannot login with this issue: https://access.redhat.com/solutions/4347301

Red Hat Enterprise Linux 9.20241008.0.4 (Plow)
Kernel 5.14.0-427.37.1.el9_4.x86_64 on an x86_64

bootc-container login: bootc-user
Password: 

Cannot make/remove an entry for the specified session

Have to check...