fix/lvm-over-raid-clear-holders-v2 : lp:~raharper/curtin : Git : Code : curtin

Get this branch:: git clone -b fix/lvm-over-raid-clear-holders-v2 https://git.launchpad.net/~raharper/curtin

Only Ryan Harper can upload to this branch. If you are Ryan Harper please log in for upload directions.

Branch merges

Merged into curtin:master

Server Team CI bot: Approve (continuous-integration) on 2019-12-10

Dan Watkins (community): Approve on 2019-12-09

Branch information

Name:: fix/lvm-over-raid-clear-holders-v2

Repository:: lp:~raharper/curtin

Recent commits

ada7056... by Ryan Harper on 2019-12-10

Fix typo in clear-holders plan shutdown comment

f5f42ec... by Ryan Harper on 2019-12-06

Reword comment on sorting the holder tree shutdown plan result.

083eabd... by Ryan Harper on 2019-12-06

Refactor devtype ordering function for readability and reliability

8d6522e... by Ryan Harper on 2019-12-06

Move comment under else clause

de1a3e4... by Ryan Harper on 2019-12-06

Replace map() with list comprehension

be04725... by Ryan Harper on 2019-11-20

clear-holders: holders are lists of holder-trees

It turns out that the holders list contains other holder
trees so length of the list is not sufficient to determine the
depth. Recurse into the holder list to extract the full depth.

54cadde... by Ryan Harper on 2019-11-19

clear-holders: handle arbitrary order of devices to clear

At some point, the vmtest for LVM over bcache was sorted in a way
that exposed the level calculation and missed that the lvm device
does not have any holders, but because it is on-top of a bcache
layer must be shutdown first. Resolve this by two changes: First
we now sort the holders trees so we have a consistent plan. Second
when adding devices to the shutdown registry, if the device has not
been seen we take the max of either the current level, or the size
of the devices holders.

95197ff... by Daniel Fox <email address hidden> on 2019-11-13

Fix parsing of squashfs: uri prefix for installation sources

util.santitize_source was truncating uris which used the squashfs:
prefix by taking the index of a character rather than a slice starting
at that character. This changes fixes this issue and provides the
intended behaviour and adds a deprecation warning to point to
the supported URI: "squashfs://".

LP: #1851271

48a476b... by Ryan Harper on 2019-11-05