volume group creation fails on md device - MAAS 3.2
Bug #1981536 reported by
Lirim
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Anton Troyanov | ||
3.2 |
Fix Released
|
High
|
Anton Troyanov |
Bug Description
With Maas 3.2 (snap) creating a volume group on top of previously configured RAID device (0 or 1) is failing with:
errorlist Select a valide choice.722 is not one of the available choices.
Step to reproduce:
On Maas dashboard:
- Commission a machine with 3 disks
- Under Storage, create a RAID 0 or 1 from two of the disks
- Try creating a volume group on top of newly created md0 device
However creating a volume group directly on the disks works. Also with Maas 3.1 both methods seem to work.
Related branches
~troyanov/maas:revert-1938296-to-3.2
- Anton Troyanov: Approve
- MAAS Lander: Approve
-
Diff: 195 lines (+14/-57)6 files modifiedsrc/maasserver/forms/__init__.py (+3/-3)
src/maasserver/forms/tests/test_blockdevice.py (+1/-2)
src/maasserver/models/filesystemgroup.py (+0/-4)
src/maasserver/models/tests/test_filesystemgroup.py (+0/-29)
src/maasserver/models/tests/test_node.py (+3/-4)
src/maasserver/tests/test_preseed_storage.py (+7/-15)
~troyanov/maas:revert-1938296
Merged
into
maas:master
- Alberto Donato (community): Approve
- MAAS Lander: Approve
-
Diff: 195 lines (+14/-57)6 files modifiedsrc/maasserver/forms/__init__.py (+3/-3)
src/maasserver/forms/tests/test_blockdevice.py (+1/-2)
src/maasserver/models/filesystemgroup.py (+0/-4)
src/maasserver/models/tests/test_filesystemgroup.py (+0/-29)
src/maasserver/models/tests/test_node.py (+3/-4)
src/maasserver/tests/test_preseed_storage.py (+7/-15)
description: | updated |
Changed in maas: | |
milestone: | none → 3.3.0 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in maas: | |
assignee: | nobody → Anton Troyanov (troyanov) |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | 3.3.0 → 3.3.0-beta1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This seems related to the fix for LP:1938296, which creates a partition table on the raid device when a raid is created.
This makes the raid device unavailable for creating a volume group on.