subiquity shows paths, instead of the multipath device for partitioning

[Dimitri John Ledkov]

I have created a virt-manager machine, with slightly tweaked disks.

I have created a RAW disk, which i have attached twice to create multipath device.

<disk type="file" device="disk">
  <driver name="qemu" type="raw" cache="none"/>
  <source file="/var/lib/libvirt/images/raw.img"/>
  <backingStore/>
  <target dev="sda" bus="scsi"/>
  <shareable/>
  <serial>5002e10000000000</serial>
  <wwn>0x5000c50015ea71aa</wwn>
  <alias name="scsi0-0-0"/>
  <address type="drive" controller="0" bus="0" target="0" unit="0"/>
</disk>

<disk type="file" device="disk">
  <driver name="qemu" type="raw" cache="none"/>
  <source file="/var/lib/libvirt/images/raw.img"/>
  <backingStore/>
  <target dev="sdb" bus="scsi"/>
  <shareable/>
  <serial>5002e10000000000</serial>
  <wwn>0x5000c50015ea71aa</wwn>
  <alias name="scsi0-0-1"/>
  <address type="drive" controller="0" bus="0" target="0" unit="1"/>
</disk>

Full virsh config to be attached.

It looks like probe data correctly shows individual paths, the fact that they are multipathed, and the multipath target.... however subiquity in the automatic or manual partitioning only shows the paths (sda sdb) and not the multipath device (mpatha).

[Michael Hudson-Doyle (mwhudson)]

Is this fixed now?

[Dimitri John Ledkov (xnox)]

Yes, with subiquity-side / ui code filtering. Imho curtin shouldn't be giving us paths in the first place (see the multipath spec)

[Michael Hudson-Doyle (mwhudson)]

Is this really fixed now? :)