"signature hdr data: BAD, no. of bytes(11548) out of range" when installing on RHEL 8

[michaelniemand]

Tried installing on RHEL 8.1 and 8.6, error is reproducible 100%

https://kurl.sh/2ad9720 was the installer I used, tried air gapped as well as standard.

Seems to be related to: https://bugzilla.redhat.com/show_bug.cgi?id=1918777

Running transaction check
error: /var/lib/kurl/packages/kubernetes/1.27.2/rhel-8/perl-IO-Socket-SSL-2.066-4.module_el8+339+1ec643e0.noarch.rpm: signature hdr data: BAD, no. of bytes(11548) out of range
Error: error reading package header: '/var/lib/kurl/packages/kubernetes/1.27.2/rhel-8/perl-IO-Socket-SSL-2.066-4.module_el8+339+1ec643e0.noarch.rpm'
An error occurred on line 2777

Any ideas for a workaround?

edit: for reproduction purposes, here are the ami IDs for the AWS images I tried:

ami-0762a21ba1fd7c2c0 (RHEL-SAP-8.1.0_HVM-20211007-x86_64-0-Hourly2-GP2)
ami-0e7e134863fac4946 (RHEL-8.6.0_HVM-20220503-x86_64-2-Hourly2-GP2)

I also tried adding --nogpgcheck to the yum calls in the install.sh but to no avail

[ricardomaraschini]

Hi @michaelniemand, I have tried to reproduce the issue without success. When I attempt to search for the ami-0e7e134863fac4946 I found only one reference but when I select such reference AWS ends ups selecting ami-06640050dc3f556bb instead (also a RHEL 8.6). I suspect that this AMI was replaced by a more updated version.

Would you mind checking if in your system these are the versions you have installed? You can find them by running rpm -q <package>, e.g. rpm -q rpm.

rpm-4.14.3-23.el8.x86_64
dnf-4.7.0-8.el8.noarch
yum-4.7.0-8.el8.noarch

You can also try to update these dependencies and attempt a new install. With the above mentioned versions I manage to install.

[michaelniemand]

the AMI is the same build, just a different region (yours is us-east-1, mine is eu-central-1)

as for the versions I get:

rpm-4.14.3-23.el8.x86_64
dnf-4.7.0-8.el8.noarch
yum-4.7.0-8.el8.noarch

so exact same as you... weird. I was able to successfully install k8s yesterday with an older k8s version though (1.24.15).

Could it be that the rpm packages in the airgap bundle for k8s 1.27 have been built with a newer rpm version than the older ones? That seems to be common source of this error as well?

[ricardomaraschini]

@michaelniemand I have been able to reliably reproduce this using RHEL 8.1. The problem has been addressed in our main branch, we just need to wait for a release now. Thanks for reporting it back to us.