Bug 1172472

Summary:	Use "leavebootorder" as a default kernel option for PPC hardware
Product:	[Retired] Beaker	Reporter:	Amit Saha <asaha>
Component:	general	Assignee:	Dan Callaghan <dcallagh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	aigao, dcallagh, dowang, ebaak, rjoost
Target Milestone:	21.1	Keywords:	FutureFeature, Patch
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-21 03:25:49 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 Amit Saha 2014-12-10 06:38:07 UTC

Description of problem:

Currently, on PPC hardware (ppc/ppc64/ppc64le), Beaker passes the "--leavebootorder" switch to the "bootloader" kickstart command to preserve the boot order on the system. However, this approach doesn't work if a custom kickstart is used and hence per system install option needs to be set by the system admins to make sure that the boot order is not fiddled with by the installer and users using custom kickstarts do not suffer.

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


How reproducible:

Always

Steps to Reproduce:

1. Grab a system which is one of the PPC archs above
2. Clear out any system kernel option set
3. Provision it using a custom kickstart without passing the "leavebootorder" switch to "bootloader".
4. The system boot order should have been changed such that the hard disk is the first boot device.

Actual results:

(4) above


Expected results:

The boot order remains the same: the first device should be the network device and the second device, the secondary storage device.

Additional info:

Beaker should instead use "leavebootorder" as a default kernel option so that the per system configuration is not required, thus making the lives of system admins slightly better.

Comment 1 Dan Callaghan 2014-12-10 23:56:23 UTC

We should probably use "leavebootorder" kernel option *and* "bootloader --leavebootorder" kickstart command (not instead of), just to cover all our bases. There should be no harm in having both.

Comment 2 Amit Saha 2014-12-11 00:02:41 UTC

(In reply to Dan Callaghan from comment #1)
> We should probably use "leavebootorder" kernel option *and* "bootloader
> --leavebootorder" kickstart command (not instead of), just to cover all our
> bases. There should be no harm in having both.

Indeed!

Comment 4 Dan Callaghan 2015-10-07 07:30:10 UTC

http://gerrit.beaker-project.org/4426

Comment 7 Dan Callaghan 2015-10-21 03:25:49 UTC

Beaker 21.1 has been released.