Pick up wrong grub.cfg if another filesystem exists
Bug #1582070 reported by
Ike Panhc
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Newell Jensen | ||
1.9 |
Fix Released
|
Medium
|
Newell Jensen | ||
2.0 |
Fix Released
|
Medium
|
Newell Jensen |
Bug Description
With BMC has no capability to switch boot order from PXE to SATA, MAAS provides grub.cfg to search another grub.cfg on harddrive
set default="0"
set timeout=0
menuentry 'Local' {
echo 'Booting local disk...'
search --set=root --file /boot/grub/grub.cfg
configfile /boot/grub/grub.cfg
}
But if another filesystem is there and unfortunately an /boot/grub/grub.cfg on it, e.g. an Ubuntu installer CDROM or usb stick. Grub might pick up wrong grub.cfg and deploying will fail.
Related branches
lp:~newell-jensen/maas/fix-1582070
- Blake Rouse (community): Approve
-
Diff: 12 lines (+2/-2)1 file modifiedetc/maas/templates/uefi/config.local.arm64.template (+2/-2)
lp:~newell-jensen/maas/2.0-fix-1582070
- Newell Jensen (community): Approve
-
Diff: 12 lines (+2/-2)1 file modifiedetc/maas/templates/uefi/config.local.arm64.template (+2/-2)
lp:~newell-jensen/maas/1.9-fix-1582070
- Newell Jensen (community): Approve
-
Diff: 12 lines (+2/-2)1 file modifiedetc/maas/templates/uefi/config.local.arm64.template (+2/-2)
Changed in maas: | |
assignee: | nobody → Newell Jensen (newell-jensen) |
tags: | added: hs-arm64 |
tags: | added: arm64 |
Changed in maas: | |
importance: | Undecided → Medium |
summary: |
- Pick up wrong grub.cfg if another filesystem exist + Pick up wrong grub.cfg if another filesystem exists |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | none → next |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Changed in maas: | |
milestone: | next → none |
To post a comment you must log in.
We faced this issue, because a USB stick that happened to have an Ubuntu image on it was placed into the server being controlled by MAAS. The server then started to misbehave when MAAS deployments were made. The issue took a *long* time to root cause, and we believe this behaviour makes MAAS significantly more fragile.
In a real world environment, we don't believe this would be a particularly unusual sequence of events.