On Sat, 18 Apr 2020 at 08:50, Ryan Harper <email address hidden>
wrote:
> The 'path' key in the disks results in curtin resolving the path to the
> disk differently; since sdb does have a holder (multipath layer) we
> attempt to clear and wipe the partitions, however since they are path
> members, we cannot write to them directly.
>
> Now that I can recreate I can start working on a fix for this. I think
> I'll need to convert more of our vmtests to using the path key (which is
> unstable for us in VMs but in practice for subiquity it is stable).
> Something to discuss on emitted config here I think.
>
subiquity only emits path in the disk config to avoid having logic to care
about only emitting it if there is no serial -- I assumed that if serial
was there curtin entirely ignored the path. If that's not true, we can
change stuff.
On Sat, 18 Apr 2020 at 08:50, Ryan Harper <email address hidden>
wrote:
> The 'path' key in the disks results in curtin resolving the path to the
> disk differently; since sdb does have a holder (multipath layer) we
> attempt to clear and wipe the partitions, however since they are path
> members, we cannot write to them directly.
>
> Now that I can recreate I can start working on a fix for this. I think
> I'll need to convert more of our vmtests to using the path key (which is
> unstable for us in VMs but in practice for subiquity it is stable).
> Something to discuss on emitted config here I think.
>
subiquity only emits path in the disk config to avoid having logic to care
about only emitting it if there is no serial -- I assumed that if serial
was there curtin entirely ignored the path. If that's not true, we can
change stuff.