curtin

curtin doesn't handle 'preserve' for raid devices

Bug #1522147 reported by Ryan Harper
6
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 modified
curtin/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)
lp:~curtin-dev/curtin/trunk
lp:~smoser/ubuntu/trusty/curtin/trusty-proposed
Ryan Harper (raharper)
Changed in curtin:
importance: Undecided → Medium
status: New → Triaged
Scott Moser (smoser)
Changed in curtin:
assignee: nobody → Ryan Harper (rharper)
Revision history for this message
Scott Moser (smoser) wrote :

fix-committed in revno 330.

Changed in curtin:
status: Triaged → Fix Committed
Revision history for this message
Scott Moser (smoser) wrote : Fixed in Curtin 17.1

This bug is believed to be fixed in curtin in 17.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in curtin:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.