I am also affected by this bug (using 22.04 LTS server with cloud-init autoinstall).
Problem seems to be that dmsetup reports only file name of the device file (e.g. nvme0n1p3 without the /dev/ prefix) but curtin expects the full path of the device file (e.g. /dev/nvme0n1p3 including /dev/ prefix)
I don't see how to tell dmsetup to include full path when reporting the blkdevs_used field. Thus, I'd assume curtin should drop the directory part from its expectation or at least make it optional.
Problem seems to still exist in current subiquity, at least it still fails when
refresh-installer:
update: yes
updates to snap-version 23.10.1
BTW: I'd be happy to test. Where can I find the patch (and possibly instruction of how to install the patch on 22.04 LTS iso?)
I am also affected by this bug (using 22.04 LTS server with cloud-init autoinstall).
Problem seems to be that dmsetup reports only file name of the device file (e.g. nvme0n1p3 without the /dev/ prefix) but curtin expects the full path of the device file (e.g. /dev/nvme0n1p3 including /dev/ prefix)
I don't see how to tell dmsetup to include full path when reporting the blkdevs_used field. Thus, I'd assume curtin should drop the directory part from its expectation or at least make it optional.
Problem seems to still exist in current subiquity, at least it still fails when
refresh- installer:
update: yes
updates to snap-version 23.10.1
BTW: I'd be happy to test. Where can I find the patch (and possibly instruction of how to install the patch on 22.04 LTS iso?)