Actually I've got around this problem by deleting sda5 which was small swap partition and successfully installed system (after tweaking system datetime cause without Internet access datetime on server was Jan 2018 and installer complained on invalid Ubuntu certificate and failed).
But I was able to reproduce problem on VirtualBox. Here is steps to do it: 1. Create virtual machine with two disks - on first (20 GB for example) create msdos partition table (I used gparted from ubuntu-19.10-desktop-amd64.iso) with 1 primary partition (I've created 18.5 GB ext4, it will be sda1) and 1 extended partition (sda2) consisting of 1 logical partition (e.g. 1.5 GB swap, sda5), second leave as is (sdb, I've created 10 GB disk). 2. Load VM from ubuntu-18.04.3-live-server-amd64.iso, pass to disk selection, select entire disk and choose second one (sdb, without partitions), apply (settings should looke like this https://ibb.co/YZBSMvR), curtin will start to work and will fail just like on our physical server (https://ibb.co/4f4rJRY, https://ibb.co/nfQ8S0z). Attached /var/log/installer/subiquity-curtin-install.conf as Ryan Harper have asked. ** Attachment added: "subiquity-curtin-install.conf" https://bugs.launchpad.net/curtin/+bug/1861251/+attachment/5324077/+files/subiquity-curtin-install.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861251 Title: 'extended_part_no' referenced before assignment error during install To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1861251/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
