kernel options not showing up in WebUI and not being passed at install time to one node
Bug #1249435 reported by
Liam Young
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Julian Edwards |
Bug Description
I have a Global Kernel Parameter set but one of my nodes its not showing it in the WebUI (it shows for all other nodes). Also it doesn't seem to be being passed when the node installs or boots subsequently.
All nodes are in the "ready" state
I've tried removing the kernel option and adding it back in again
maas-cli seems to returns the correct value
$ maas-cli maas maas get-config name=kernel_opts
"console=ttyS1"
Related branches
lp:~julian-edwards/maas/effective-kernel-opts-bug-1249435
- Gavin Panella (community): Needs Fixing
- Jeroen T. Vermeulen (community): Approve
-
Diff: 41 lines (+11/-2)2 files modifiedsrc/maasserver/models/node.py (+1/-1)
src/maasserver/models/tests/test_node.py (+10/-1)
Changed in maas: | |
status: | Incomplete → Triaged |
importance: | Undecided → High |
Changed in maas: | |
assignee: | nobody → Julian Edwards (julian-edwards) |
milestone: | none → 14.04 |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
If there's a tag associated with the node that specifies kernel opts, it takes precedence over the global options. Could that be happening here? A tag that used to have kernel options set but which you removed? (This latter scenario seems probable; the Tag.kernel_opts field is defined as being blank or null, but the query for effective kernel options only considers nullness.)
Fwiw, if more than one tag with kernel options applies to a node, only the first tag, when sorted by name in lexicographical order, with kernel options is used.