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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1872941

Title:
  [Ubuntu 20.04] virt-install fails to detect path after images folder
  name has changed

Status in Ubuntu CD Images:
  Opinion
Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in virt-manager package in Ubuntu:
  Invalid

Bug description:
  Installer version: Latest
  https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

  Description/Reproduction:
  Start virt-install with the following options:

  virt-install \
  --name ubuntu20-guest1 \
  --memory 4096 \
  --vcpus 4 \
  --disk "size=4" \
  --location 
http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x \
  --network "network=default" 

  Error:
  ERROR    Error validating install location: Could not find an installable 
distribution at 
'http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x'

  The location must be the root directory of an install tree.
  See virt-install man page for various distro examples.

  
  Looking at previous releases I would guess it expects an "images" directory 
instead of the new "classic-images" directory. I'm aware of the workaround to 
specify kernel/initramfs directly but that shouldn't be a solution.

  == Comment: #2 - Andre Wild1 <andre.wi...@ibm.com> - 2020-04-15 03:51:21 ==
  (In reply to comment #0)
  > Installer version: Latest
  > https://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x
  > 

  Sorry I've copied the wrong link. This is the link I've used successfully in 
the past:
  http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/installer-s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1872941/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to