Bug 1278229 - [RFE] ksmeta variable to control bootloader --driveorder option
[RFE] ksmeta variable to control bootloader --driveorder option
Status: NEW
Product: Beaker
Classification: Community
Component: general (Show other bugs)
21
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: beaker-dev-list
tools-bugs
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-04 20:40 EST by Dan Callaghan
Modified: 2015-11-04 20:40 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dan Callaghan 2015-11-04 20:40:33 EST
Anaconda has the --driveorder option to the bootloader command, in cases where the first hard disk (from kernel point of view) is not actually the boot device for the system. --driveorder lets us tell Anaconda to install the boot loader on some other device instead.

It would be useful if Beaker had a ksmeta variable specifically for controlling this option.

Note You need to log in before you can comment on or make changes to this bug.