Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2139408

Summary:	After reboot a RHV-H host fails to boot displaying error: ../../grub-core/loader/i386/pc/linux.c:170:invalid magic number
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Raul Aldaz <raldaz>
Component:	imgbased	Assignee:	Asaf Rachmani <arachman>
Status:	CLOSED WORKSFORME	QA Contact:	peyu
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.4.10	CC:	arachman, cshao, godas, lleistne, mavital, michal.skrivanek, mperina, peyu, weiwang, yaniwang
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-12-14 12:17:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Raul Aldaz 2022-11-02 12:33:44 UTC

Description of problem:

- kernel image and initramfs files were truncated to 0 bytes on "/boot/rhvh-4.4.10.1-0.20220208.0+1" after Host reboot. On boot, bellow error is found in serial console:

~~~
error: ../../grub-core/loader/i386/pc/linux.c:170:invalid magic number.
error: ../../grub-core/loader/i386/pc/linux.c:421:you need to load the kernel first.

Press any key to continue...
~~~


Version-Release number of selected component (if applicable):

RHV-H 4.4.10.1 (kernel 4.18.0-348.12.2) after upgrade from RHV-H 4.4.9.4 (kernel 4.18.0-348.7.1)

How reproducible:

Always on customer environment

Steps to Reproduce:
1. Reboot Host after mentioned upgrade.

Actual results:

- Mentioned error message on boot.

Expected results:

- Usual boot without truncated files 

Additional info:

- Seems like a recurring issue according to https://bugzilla.redhat.com/show_bug.cgi?id=1931443

Comment 1 peyu 2022-11-03 06:37:47 UTC

QE tried to reproduce this bug without success.

Test version:
RHVM: 4.4.10.7-0.4.el8ev
RHVH: redhat-virtualization-host-4.4.9-202201072228_8.5
      redhat-virtualization-host-4.4.10-202202081536_8.5

Test steps:
1. Install RHVH-4.4-20220110.0-RHVH-x86_64-dvd1.iso
2. Set up local repo and point to "redhat-virtualization-host-4.4.10-202202081536_8.5"
3. Add the host to RHVM
3. Upgrade the host via RHVM portal
4. Check the host status after upgrade
   

Test result:
The host upgrade was successful, and after rebooting, it entered the new layer rhvh-4.4.10.1-0.20220208.0+1 without any error message.

~~~~~~
# imgbase w
You are on rhvh-4.4.10.1-0.20220208.0+1


# imgbase layout
rhvh-4.4.9.4-0.20220107.0
 +- rhvh-4.4.9.4-0.20220107.0+1
rhvh-4.4.10.1-0.20220208.0
 +- rhvh-4.4.10.1-0.20220208.0+1
~~~~~~

Additional info:

Comment 2 peyu 2022-11-03 06:48:50 UTC

I checked this bug you mentioned:  https://bugzilla.redhat.com/show_bug.cgi?id=1931443
Is the customer's environment running RHHI?

Did you notice this documented workaround below?
https://access.redhat.com/solutions/5829141

Comment 13 Michal Skrivanek 2022-12-14 12:17:49 UTC

seems to be working on in latest version, though we're not ableto reproduce the exact scenario
Please feel free to reopen if it keeps happening and there is more information