Bug 1832255

Summary: [Baremetal] console parameter on PXE configuration is not persistent after installing
Product: OpenShift Container Platform Reporter: David Sanz <dsanzmor>
Component: RHCOSAssignee: Micah Abbott <miabbott>
Status: CLOSED DUPLICATE QA Contact: Michael Nguyen <mnguyen>
Severity: high Docs Contact:
Priority: high    
Version: 4.5CC: bbreard, imcleod, jligon, nstielau
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: 2020-05-06 18:53:38 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 David Sanz 2020-05-06 11:42:23 UTC
Description of problem:

We cant follow installations of RHCOS on baremetal. HW provider requires special configuration of console, provided on PXE for installation as:

console=ttyS1,115200n8 console=tty0

The only line shown after booting is:

Probing EDD (edd=off to disable)... ok                                          �


Watching at grub linux line, console configuration is different than especified on PXE:

console=tty0 console=ttyS0,115200n8


Version-Release number of selected component (if applicable):
RHCOS 45.81.202005022156-0
Installer: 4.5.0-0.nightly-2020-05-06-003431

How reproducible:


Steps to Reproduce:
1.Install Baremetal using PXE with custom console parameters
2.Check console line editing grub line before starting
3.

Actual results:
console parameters configured on PXE are not passed to grub

Expected results:
console parameters are considered to configure grub

Additional info:

Comment 1 Micah Abbott 2020-05-06 18:53:38 UTC
This is mostly a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1712511 which started out as discussing how to change console settings, but has been repurposed for the general problem of persisting kargs.

*** This bug has been marked as a duplicate of bug 1712511 ***