Bug 1994275

Summary: The vmlinuz and initrd are always 0 size
Product: Red Hat Satellite Reporter: Kenny Tordeurs <ktordeur>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Stephen Wadeley <swadeley>
Severity: high Docs Contact:
Priority: medium    
Version: 6.10.0CC: dalley, ggainey, iballou, inecas, jjansky, jsherril, mmccune, osousa, patalber, pcreech, rchan, saydas, sshtein, ttereshc
Target Milestone: 6.10.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: python-pulp-rpm-3.14.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-16 14:13:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kenny Tordeurs 2021-08-17 08:08:46 UTC
Description of problem:
The vmlinuz and initrd are always 0 size when being created.

Version-Release number of selected component (if applicable):
satellite-6.10.0-0.6.beta.el7sat.noarch

How reproducible:
On my env 100%

Steps to Reproduce:
1. Sync RHEL 7.9 kickstart on_demand
2. Create a host
3. Build fails, vmlinuz and initrd are 0 size

Actual results:
[root@ktordeur-testathon boot]# ls -ltr
total 0
-rw-r--r--. 1 foreman-proxy foreman-proxy 0 Aug 17 09:59 red-hat-enterprise-linux-7-server-kickstart-x86_64-7-9-41-vmlinuz
-rw-r--r--. 1 foreman-proxy foreman-proxy 0 Aug 17 09:59 red-hat-enterprise-linux-7-server-kickstart-x86_64-7-9-41-initrd.img


Expected results:
The files to be generated correctly

Additional info:
Removing the files, resyncing the repo and redoing the build ends up with 0 size again.

Comment 1 Kenny Tordeurs 2021-08-17 12:43:46 UTC
Default Organization View is being used if that information is important.

Comment 2 Kenny Tordeurs 2021-08-18 07:28:17 UTC
Also attempted to sync with immediate, remove boot files, however they are still re-generated as 0 size files.
This is a blocker for provisioning to work.

Comment 3 Jan Jansky 2021-08-18 07:31:31 UTC
I had reproduced the same, before first sync i set kickstart repositories to download policy immediate, synchronized, published and promoted CV, when i created host new vmlinuz and initrd files was created, but both have 0 size as below

# ls -al /var/lib/tftpboot/boot/
total 4
drwxr-xr-x. 2 foreman-proxy root           155 17. srp 15.41 .
drwxr-xr-x. 8 root          root          4096 17. srp 13.03 ..
-rw-r--r--. 1 foreman-proxy foreman-proxy    0 17. srp 15.41 red-hat-enterprise-linux-7-server-kickstart-x86_64-7-9-27-initrd.img
-rw-r--r--. 1 foreman-proxy foreman-proxy    0 17. srp 15.41 red-hat-enterprise-linux-7-server-kickstart-x86_64-7-9-27-vmlinuz

Comment 4 Ondrej Gajdusek 2021-08-18 15:53:36 UTC
This bug seems to be connected with BZ1992329.

The workaround for this bug is to set 'Mirror on Sync' to 'No' for the kickstart repo and resync it, cancel build of the host and Build the host again.

Comment 5 Sayan Das 2021-08-19 08:04:44 UTC
This is what I found:

* Enable RHEL 8 BaseOS kickstart and sync it. Result: 404 not found for vmlinuz and initrd

Aug 19 13:04:38 satellite pulpcore-content: [19/Aug/2021:07:34:38 +0000] "GET /pulp/content/RedHat/Library/content/dist/rhel8/8.4/x86_64/baseos/kickstart/images/pxeboot/vmlinuz HTTP/1.1" 404 172 "-" "rest-client/2.0.2 (linux x86_64) ruby/2.7.3p183"
Aug 19 13:04:38 satellite pulpcore-content: [19/Aug/2021:07:34:38 +0000] "GET /pulp/content/RedHat/Library/content/dist/rhel8/8.4/x86_64/baseos/kickstart/images/pxeboot/initrd.img HTTP/1.1" 404 172 "-" "rest-client/2.0.2 (linux x86_64) ruby/2.7.3p183"


* Content --> Products --> Red Hat Enterprise Linux for x86_64 --> Repositories --> Click open Red Hat Enterprise Linux 8 for x86_64 - BaseOS Kickstart 8.4  --> From Select Action dropdown Select "Advanced Sync" and then perform "Complete Sync"


Result: 200: Downloaded 


Aug 19 13:29:24 satellite pulpcore-content: [19/Aug/2021:07:59:17 +0000] "GET /pulp/content/RedHat/Library/content/dist/rhel8/8.4/x86_64/baseos/kickstart/images/pxeboot/vmlinuz HTTP/1.1" 200 10031579 "-" "rest-client/2.0.2 (linux x86_64) ruby/2.7.3p183"

Aug 19 13:29:45 satellite pulpcore-content: [19/Aug/2021:07:59:24 +0000] "GET /pulp/content/RedHat/Library/content/dist/rhel8/8.4/x86_64/baseos/kickstart/images/pxeboot/initrd.img HTTP/1.1" 200 75547193 "-" "rest-client/2.0.2 (linux x86_64) ruby/2.7.3p183"



So hoping that if I create a host now and Submit it for build , I should have no problem getting the good vmlinuz and initrd files.

Comment 6 Sayan Das 2021-08-19 08:08:09 UTC
(In reply to Sayan Das from comment #5)
> This is what I found:
> 
> * Enable RHEL 8 BaseOS kickstart and sync it. Result: 404 not found for
> vmlinuz and initrd
> 
> Aug 19 13:04:38 satellite pulpcore-content: [19/Aug/2021:07:34:38 +0000]
> "GET
> /pulp/content/RedHat/Library/content/dist/rhel8/8.4/x86_64/baseos/kickstart/
> images/pxeboot/vmlinuz HTTP/1.1" 404 172 "-" "rest-client/2.0.2 (linux
> x86_64) ruby/2.7.3p183"
> Aug 19 13:04:38 satellite pulpcore-content: [19/Aug/2021:07:34:38 +0000]
> "GET
> /pulp/content/RedHat/Library/content/dist/rhel8/8.4/x86_64/baseos/kickstart/
> images/pxeboot/initrd.img HTTP/1.1" 404 172 "-" "rest-client/2.0.2 (linux
> x86_64) ruby/2.7.3p183"
> 
> 
> * Content --> Products --> Red Hat Enterprise Linux for x86_64 -->
> Repositories --> Click open Red Hat Enterprise Linux 8 for x86_64 - BaseOS
> Kickstart 8.4  --> From Select Action dropdown Select "Advanced Sync" and
> then perform "Complete Sync"
> 
> 
> Result: 200: Downloaded 
> 
> 
> Aug 19 13:29:24 satellite pulpcore-content: [19/Aug/2021:07:59:17 +0000]
> "GET
> /pulp/content/RedHat/Library/content/dist/rhel8/8.4/x86_64/baseos/kickstart/
> images/pxeboot/vmlinuz HTTP/1.1" 200 10031579 "-" "rest-client/2.0.2 (linux
> x86_64) ruby/2.7.3p183"
> 
> Aug 19 13:29:45 satellite pulpcore-content: [19/Aug/2021:07:59:24 +0000]
> "GET
> /pulp/content/RedHat/Library/content/dist/rhel8/8.4/x86_64/baseos/kickstart/
> images/pxeboot/initrd.img HTTP/1.1" 200 75547193 "-" "rest-client/2.0.2
> (linux x86_64) ruby/2.7.3p183"
> 
> 
> 
> So hoping that if I create a host now and Submit it for build , I should
> have no problem getting the good vmlinuz and initrd files.


And confirming that, I can see good files now.

# ll /var/lib/tftpboot/boot/
total 83556
drwxr-xr-x. 2 foreman-proxy root               139 Aug 19 11:21 fdi-image
-rw-r--r--. 1 foreman-proxy foreman-proxy 75530980 Aug 19 13:29 red-hat-enterprise-linux-8-for-x86_64-baseos-kickstart-8-4-12-initrd.img
-rw-r--r--. 1 foreman-proxy foreman-proxy 10026352 Aug 19 13:29 red-hat-enterprise-linux-8-for-x86_64-baseos-kickstart-8-4-12-vmlinuz

# md5sum /var/lib/tftpboot/boot/*8*
8742254063554f774844c8a1b1b7af53  /var/lib/tftpboot/boot/red-hat-enterprise-linux-8-for-x86_64-baseos-kickstart-8-4-12-initrd.img
3b95cceb4a3d43e1ce9cd7beda8e3f4f  /var/lib/tftpboot/boot/red-hat-enterprise-linux-8-for-x86_64-baseos-kickstart-8-4-12-vmlinuz

# file /var/lib/tftpboot/boot/*8*
/var/lib/tftpboot/boot/red-hat-enterprise-linux-8-for-x86_64-baseos-kickstart-8-4-12-initrd.img: XZ compressed data
/var/lib/tftpboot/boot/red-hat-enterprise-linux-8-for-x86_64-baseos-kickstart-8-4-12-vmlinuz:    Linux kernel x86 boot executable bzImage, version 4.18.0-305.el8.x86_64 (mockbuild.eng.bos.redhat, RO-rootFS, swap_dev 0x9, Normal VGA



So I haven't changed anything else for the enabled repo config but simple did "Complete Sync" which is sync by skipping metadata check

Comment 7 Justin Sherrill 2021-08-19 13:29:24 UTC
This is likely a duplicate of this bz: https://bugzilla.redhat.com/show_bug.cgi?id=1992329

Comment 8 Tanya Tereshchenko 2021-08-19 20:01:45 UTC
I agree that the root cause is the same as in https://bugzilla.redhat.com/show_bug.cgi?id=1992329 but suggest to keep it for QE testing.

Comment 9 Daniel Alley 2021-08-22 02:53:13 UTC
Agreed that this is duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1992329

However, after fixing ^^ upstream so that it no longer 404s, I still notice some weirdness with these two files.  Therefore I suggest keeping it open until we finish investigating this new (potential, unconfirmed) issue.

Comment 10 pulp-infra@redhat.com 2021-08-23 21:06:56 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.

Comment 11 pulp-infra@redhat.com 2021-08-23 21:06:57 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.

Comment 12 Mike McCune 2021-08-24 16:29:24 UTC
The workaround for this may be the same as in 1992329:

"Workaround is to set 'Mirror on Sync' to 'No' for the kickstart repo and resync it (then the missing files are synced properly). Consequential Capsule sync succeeds."

Comment 13 Sayan Das 2021-08-24 16:31:51 UTC
For me, Simply doing a "Complete Sync" fixed the issue as well as I had mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1994275#c5 .

I hadn't faced any issues with host deployment after doing so.

Comment 14 Daniel Alley 2021-08-24 16:40:05 UTC
There's a separate issue that results in trouble downloading these two files for some clients, I'm not sure if Anaconda would be impacted or not.  If it does, there is a workaround, which is to download the file with wget (from Pulp), after which it works fine.

Comment 15 Justin Sherrill 2021-08-24 17:03:58 UTC
Daniel, Katello actually fetches those files manually at sync time already to work around some issues from long ago

Comment 16 Tanya Tereshchenko 2021-08-24 17:19:23 UTC
Justin, thanks for clarification, then taking into consideration your comment#15, this BZ should be resolved with just https://pulp.plan.io/issues/9270

Comment 17 pulp-infra@redhat.com 2021-08-24 20:08:19 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.

Comment 18 pulp-infra@redhat.com 2021-08-24 21:07:18 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.

Comment 19 pulp-infra@redhat.com 2021-08-24 22:08:17 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.

Comment 23 errata-xmlrpc 2021-11-16 14:13:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.10 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:4702