[2.6,UI] First partition gets created as part2 on large disks

Bug #1821310 reported by Björn Tillenius
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Medium
Unassigned

Bug Description

This is with MAAS master as 086c3912d72026e59d7793a7080671dfb2a4c493.

I commissioned a machine with 6 disks and removed the / mount point and the first partition of sda.

Now, when I go and create a partition for another disk, it says that the created partition will be part1, as expected. But when I go ahead and create the partition, it's shown as part2.

The underlying issue is that for disks using GPT, we reserve one
partition for the BIOS partition. But hiding that, and simply
show that the first partition is part2 is very confusing.

See attached screenshots.

Tags: ui
Revision history for this message
Björn Tillenius (bjornt) wrote :
Revision history for this message
Björn Tillenius (bjornt) wrote :
description: updated
Changed in maas:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Lee Trager (ltrager)
milestone: none → 2.6.0
Revision history for this message
Blake Rouse (blake-rouse) wrote :

This is actually a UI error, it should show as it will be creating part2 not part1. That is because a disk that uses a GPT partition always reserves part1 for a bios_boot partition. That partition is not modifiable by the user or useful in anyway so its not presented in the UI or the API.

All partitions created on a GPT partition table start at part2 and go from there.

tags: added: ui
summary: - [2.6] First partition gets created as part2
+ [2.6,UI] UI shows first partition as part1 on GPT table when it should
+ be part2
Changed in maas:
importance: High → Medium
Revision history for this message
Björn Tillenius (bjornt) wrote : Re: [2.6,UI] UI shows first partition as part1 on GPT table when it should be part2

Oh. Well, I don't think the solution is to change the UI to show that part2 will be created. It's still very confusing that there's no part1. Even though the BIOS/EFI partitions can't be modified, it should be shown, so that it's clear what's happening.

And actually, do we really create a BIOS partition for non-boot disks?

Changed in maas:
assignee: Lee Trager (ltrager) → nobody
summary: - [2.6,UI] UI shows first partition as part1 on GPT table when it should
- be part2
+ [2.6,UI] First partition gets created as part2 on large disks
description: updated
Revision history for this message
Blake Rouse (blake-rouse) wrote :

Yes it is always created even if the disk is not a boot disk. Because based on the RAID configuration other disks can still end up with GRUB installed to allow for failure of a RAID disk, and keeping the system still bootable.

I disagree that the partition should be shown. A simple info message saying why it starts at part2 should be enough. Its unusable and completely out of control of the user.

Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
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.