Renaming the artefacts was a compromise. the other option was to not publish them at all.
d-i artefacts will not exist for 20.10 release, nor for 20.04.1 release, on any architecture. Thus renamed d-i artefacts is a transitional period of ~3 months until 20.04.1 is released. cloud-images for s390x with working cloud-init existed since the pre- release of the very first s390x architecture build. And work with xenial, bionic, and focal, and all intermediate releases. Why is using cloud-images not suitable for your test team which works for all Ubuntu s390x releases, and are pre-built and refreshed for every new kernel SRU? Unlike the d-i based images which are only refreshed every 6 months? https://cloud-images.ubuntu.com/ are genuinely more up to date, and are quicker to provision than d-i based installs. There are tested/curated release streams with ~2-3 week cadence, and daily streams which are updated ~1-3 days, with all packages up to date from the first boot. Can we help you move away from virt-instal d-i, to booting cloud images with any configuration applied on first-boot with cloud-init? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872941 Title: [Ubuntu 20.04] virt-install fails to detect path after images folder name has changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1872941/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
