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

Bug 1972023

Summary: Defined kernel options go missing when rhv-h is upgraded
Product: Red Hat Enterprise Virtualization Manager Reporter: Marcus West <mwest>
Component: ovirt-engineAssignee: Lev Veyde <lveyde>
Status: CLOSED ERRATA QA Contact: Pavol Brilla <pbrilla>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4.6CC: ahadas, arachman, cshao, delfassy, dfediuck, dfodor, gdeolive, lsvaty, lveyde, mavital, michal.skrivanek, mperina, peyu, sbonazzo, shlei, weiwang, yaniwang
Target Milestone: ovirt-4.4.8   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-09-08 14:12:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marcus West 2021-06-15 05:07:47 UTC
## Description of problem:

When updating rhv-h via the RHV gui, defined kernel options go missing

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

ovirt-engine-4.4.3.12-0.1.el8ev.noarch
rhvh-4.4.6.1-0.20210527.0 (new version)
rhvh-4.4.3.1-0.20201116.0 (previous version)

## How reproducible:

Always

## Steps to Reproduce:
1. Add a new host, with defined kernel options (ie "console=tty0 console=ttyS1,115200")
2. Reboot to ensure host has booted with defined kernel options
3. put host back into maintenance and upgrade

## Actual results:

The system comes up into new image, but without the defined kernel options present ("console=tty0 console=ttyS1,115200")

## Expected results:

When upgrading via the gui, the host should maintain the previously defined kernel options.

## Additional info:

If i put the host back into maintenance again, do a 'Reinstall' via the gui, then reboot, kernel options are back.  Is the user expected to perform this additional step each time?

It's unclear if this was working at some point then stopped, or if it never worked after the first rhv-h 4.4 host was initialy installed.

Comment 5 Sandro Bonazzola 2021-06-15 06:39:04 UTC
Lev, is this handled by imgbased or should it be handled by ansible upgrade code on the engine side?

Comment 7 Lev Veyde 2021-06-15 15:03:57 UTC
I tested this with CentOS, and it looks like even there the options don't survive kernel upgrade - they're only applied to the default kernel, and don't appear for the upgraded one.

Moving to infra.

Comment 9 Marcus West 2021-06-16 01:09:28 UTC
Thank you Lev - yes just to clarify, I was adding the kernel options by the RHV gui (click Hosts tab, click on host and press 'edit', click on 'Kernel', enter additional options in the 'Kernel command line' option (at the bottom))

Comment 11 Lev Veyde 2021-06-16 09:39:39 UTC
(In reply to Marcus West from comment #9)
> Thank you Lev - yes just to clarify, I was adding the kernel options by the
> RHV gui (click Hosts tab, click on host and press 'edit', click on 'Kernel',
> enter additional options in the 'Kernel command line' option (at the bottom))

Thanks Marcus, that's what I thought, but wanted to verify that.

Comment 14 Lev Veyde 2021-06-17 12:08:03 UTC
Sent a patch to fix the issue for RHEL/CentOS/CentOS Stream.

Another patch that will save/update the kernel args to some pre-agreed file under /boot is still required, so that imgbase could use these parameters during image upgrade.

Comment 15 Martin Perina 2021-06-17 12:50:31 UTC
Let's fix the issue for RHEL-H, doing that properly for RHV-H is an RFE.

Comment 17 Lev Veyde 2021-06-17 22:43:38 UTC
Sent another patch for saving the kernel arguments to the file, that will become the interface for the imgbase.

Comment 24 Pavol Brilla 2021-08-24 10:27:16 UTC
tested on rhel based host

Comment 29 errata-xmlrpc 2021-09-08 14:12:04 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 (RHV Manager (ovirt-engine) [ovirt-4.4.8]), 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/RHBA-2021:3460

Comment 30 meital avital 2022-08-03 20:18:35 UTC
Due to QE capacity, we are not going to cover this issue in our automation