Updates on grub systems lose track of panic=-1
Bug #1462501 reported by
Sergio Schvezov
on 2015-06-05
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Snappy | Status tracked in Trunk | |||||
| | 15.04 |
Critical
|
Sergio Schvezov | |||
| | Trunk |
Critical
|
Unassigned | |||
Bug Description
Since original panic=-1 was added to u-d-f (which I really dislike it being the drop zone for hacks to the rootfs), the grub.d configuration file gets lost on full system updates so the kernel cmd line effectively loses track of it as the partition is formatted and not copied over.
This makes the u-d-f written 50-snappy-
Related branches
lp:~sergiusens/ubuntu/wily/ubuntu-core-config/panic
- Michael Vogt: Approve on 2015-06-08
-
Diff: 25 lines (+11/-0)2 files modifieddebian/changelog (+6/-0)
etc/default/grub.d/50-system-image.cfg (+5/-0)
| Sergio Schvezov (sergiusens) wrote : | #2 |
The solution here to not lose the panic=-1 is to add this file to lp:ubuntu/ubuntu-core-config but this doesn't solve the problem of setting up a different cmd line to boot.
To post a comment you must log in.


Do we need to run update-grub btw? I was thinking on solving the azure problem of adding rootdelay=300 unsolvable, or at least involving a very different path than when some special arguments are needed on a u-boot based environment.