I think the reason LVM deploys fail is that there is already a VG with the name that is to be used, which should be deleted but isn't because the installer gets confused about which disk is which. In any case, the source of the problem is clear and the exact symptoms are not that important.
We should definitely handle this situation better. (I think arguably the udev rules should such a bogus wwn as well but I don't know as much about how things work at that level). Disk actions can provide three bits of data to find the drive: wwn, serial and path. Currently the installer just uses the first of whichever of these is provided (so in this case, the bogus wwn), but Dimitri suggested that instead it should use all provided fields, which would work much better for this bug at least. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929213 Title: Ubuntu server LVM creates clone partitions and crash installation (invalid wwn is used by udev & probert as well) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1929213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
