sgdisk and sfdisk blockers

Bug #1643621 reported by Barry Warsaw
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Image
Invalid
Critical
Unassigned

Bug Description

We use sgdisk and sfdisk to manipulate partitions, but these tools have several known limitations.

* We can't set offset=0 for a non mbr-type partition.
* We can't name change partition names for mbr-schema partitions
* We can't create partitions with alignments other than 1MiB (see LP: #1621151)

These are now fairly significant blockers for moving forward with ubuntu-image.

Revision history for this message
Barry Warsaw (barry) wrote :

I'm unmilestoning this issue from 0.12 since we won't fix/eliminate sgdisk/sfdisk for this release.

Changed in ubuntu-image:
milestone: 0.12 → none
Barry Warsaw (barry)
Changed in ubuntu-image:
milestone: none → 0.13
Revision history for this message
Barry Warsaw (barry) wrote :

Actually, based on further discussion, I'm closing this issue. Item 1 is nonsensical and really was a problem related to the abuse of the special type=mbr, which we've solved with role=bare. Item 2 was an implementation issue caused by unconditionally trying to use the volume key name in the gadget.yaml as the partition name, regardless of the schema. Now what we do there is basically just ignore the `change-name` option when trying to partition an mbr schema disk. It's ugly but workable.
We'll just deal with item 3 with its own existing LP: #1621151

Changed in ubuntu-image:
milestone: 0.13 → none
status: Confirmed → Invalid
assignee: Barry Warsaw (barry) → nobody
milestone: none → 0.13
milestone: 0.13 → none
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.