[UI, API] more control over parition naming / ordering

Bug #1818003 reported by Wouter van Bommel
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Medium
Unassigned

Bug Description

When creating partitions on a 'named' disk, there is little influence on the naming of the partition.
They get named like: <disk name>-part#.

The problem is that if an mistake has been made, e.g. a partition is added and later removed. This is not resembled in the name that is assigned to the partition. So one can end up with a disk e.g. md0 have a partition labeled like; md0-part10, as it took multiple iterations to get the partition right.

This is a problem for a roll-out, as some tools depend on consistent naming, which is not possible to get done this way.
Redoing the commissioning is not always an option, as that means that all disks have to be redone, even the ones that are fine. Which is quite time-consuming.

tags: added: canonical-bootstack
Changed in maas:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 2.6.0
summary: - more control over parition naming / ordering
+ [UI, API] more control over parition naming / ordering
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.