MAAS should not allow / to be fat32 or vfat

Bug #1918991 reported by Lee Trager
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Status tracked in 3.6
3.5
Won't Fix
Low
Unassigned
3.6
Triaged
Low
Unassigned

Bug Description

MAAS currently allows / to be fat32 or vfat. Neither of which would work for GNU/Linux or even modern versions of Windows.

Revision history for this message
Jerzy Husakowski (jhusakowski) wrote :

MAAS should constrain the selectable file systems to ones that will work. Low priority, because curtin will report an error anyway, and solving this issue will lead to reporting an invalid file system choice a bit earlier in the deployment process.

Changed in maas:
milestone: none → 3.5.0
Changed in maas:
milestone: 3.5.0 → 3.5.x
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.