There's no way to add kernel parameters to a system read

Bug #1045390 reported by Andres Rodriguez on 2012-09-03
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

One a system has been enlisted and commissioned, there's really no way to add new kernel parameters that are needed during installation. These kernel parameters are important as different hardware will required them sometimes, or for other cases such as enabling serial interfaces.

These should either be being able to add kernel parameters per system through cli/api or WebUI

Changed in maas:
importance: Undecided → Critical
Julian Edwards (julian-edwards) wrote :

How did these get added in the Cobbler world? As in, what was the user workflow? (I know it's part of the profile in Cobbler)

Changed in maas:
status: New → Triaged
Andres Rodriguez (andreserl) wrote :

Hi Julian,

In cobbler we could have done this using cobbler's CLI and cobbler's WEbUI:

sudo cobbler system edit --name <system name> --kopts "additional kernel options"

Julian Edwards (julian-edwards) wrote :


Sorry I was not clear enough in my question. When I talk about user workflow, I mean how does a user decide he wants these options, are they changed frequently, are they added at any particular point in the story? Is it part of commissioning setup or something that changes upon provisioning (eg. passed with user data) ?

Francis J. Lacoste (flacoste) wrote :

Bug #1044503 is about allowing customization of the kernel parameters for enlistment and commissioning. It's probably worth doing both at the same time.

Changed in maas:
importance: Critical → High
milestone: none → 12.10
Changed in maas:
milestone: 12.10 → 12.10-stabilization
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers