curtin doesn't handle 'preserve' for raid devices
Bug #1522147 reported by
Ryan Harper
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Fix Released
|
Medium
|
Ryan Harper |
Bug Description
When using custom storage config the user can specify a storage configuration that should be preserved, disks, lvm volgroup and lvm partitions, which need to be present for mounting devices at specific points.
Curtin doesn't yet implement a preserve value for storage type raid, and will attempt to recreate the raid device instead.
Related branches
lp:~raharper/curtin/trunk.implement_raid_preserve
- Scott Moser (community): Approve
- Server Team CI bot: Approve (continuous-integration)
-
Diff: 1691 lines (+1571/-44)4 files modifiedcurtin/block/__init__.py (+18/-0)
curtin/block/mdadm.py (+630/-0)
curtin/commands/block_meta.py (+32/-44)
tests/unittests/test_block_mdadm.py (+891/-0)
Changed in curtin: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in curtin: | |
assignee: | nobody → Ryan Harper (rharper) |
To post a comment you must log in.
fix-committed in revno 330.