In particular, /dev/dm-14 (mpathb) has 4 paths, but somehow the multipath 'paths' output does not include any of these devices. Curtin falls back to using the MP_UUID as the 'name' portion of a blockdev-id, so we see disk-mpath-36.......62.
The blockdev data for /dev/dm-14, DM_NAME is set, and set to mpathb; so adding this as an additional check for discovering the mpath name allows this to all work.
The included tarball includes the probe_data.json
With that we can reproduce the failure locally.
In particular, /dev/dm-14 (mpathb) has 4 paths, but somehow the multipath 'paths' output does not include any of these devices. Curtin falls back to using the MP_UUID as the 'name' portion of a blockdev-id, so we see disk-mpath- 36..... ..62.
The blockdev data for /dev/dm-14, DM_NAME is set, and set to mpathb; so adding this as an additional check for discovering the mpath name allows this to all work.
I'll have a branch up shortly.