[2.0b6,arm64] maas installs to USB drive if it is present instead of SSD
Bug #1592915 reported by
Manoj Iyer
This bug report is a duplicate of:
Bug #1582070: Pick up wrong grub.cfg if another filesystem exists.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Triaged
|
High
|
Unassigned |
Bug Description
My arm64 server has SSD, SD and USB drives. When I commission maas shows me possible targets as SSD (dev/sda) and SD (mmcblk0) but does not list the USB drive. I can then remove the SD drive from targets from the UI. But, when I deploy maas picks the USB drive as the install target instead of the SSD (dev/sda)even though sda-part1 and sda-part2 are the two storage file systems listed in MAAS UI it shows no other disks or available partitions. This causes maas to fail to boot from disk ie ssd (dev/sda) after deployment. The only workaround for now is to physically remove any USB.
Changed in maas: | |
status: | Incomplete → Triaged |
importance: | Critical → High |
To post a comment you must log in.
Appended lshw output and block-devices.out to the bug