Comment 6 for bug 1513085

Thanks Scott for merging the changes. These should fix the issue as soon as the new curtin is used.

@Jeffrey - FYI - there should be no MAAS code change required. But I'd recommend running all kind of tests you have to make sure everything is still fine.

Long Story short (for you to focus testing):

ISSUE 1: Partitions were actually always "requested size+1sector"
=> Now they are exactly the requested size

ISSUE 2: An extended partition always needed "requested size + 2 sectors per logical partition" and e.g. 10G partition could not fit e-g- 3G+3G+4G logical partitions
=> there are various constraints with extended partitions, to avoid these they will now "requested size + 1MB per logical partition"
=> also as "Humans would assume" 3G+3G+4G now fits into 10G

ISSUE 3: Due to the former two issues usually only the first partition was properly aligned to 1MB
=> now they are all aligned as long as the sizes you request are aligned to 1MB (which they usually are as MAAS exposes 1MB granularity)
Most issues came up with extended/logical msdos partitions, but the non-alignment issue also hit gpt partitions.