Activity log for bug #1878066

Date Who What changed Old value New value Message
2020-05-11 17:57:29 msp3k bug added bug
2020-05-11 17:57:29 msp3k attachment added Booting UEFI+grub2 with ds=nocloud-net;s=<url> https://bugs.launchpad.net/bugs/1878066/+attachment/5369987/+files/standard-focal-ds%3Dnocloud-net-s%3Durl-stuff.tar.gz
2020-05-11 17:58:46 msp3k attachment added latest daily build on 2020-05-11 with ds=nocloud-net;s=<url> https://bugs.launchpad.net/subiquity/+bug/1878066/+attachment/5369988/+files/standard-groovy-ds%3Dnocloud-net-s%3Durl-stuff.tar.gz
2020-05-11 18:00:11 msp3k attachment added Booting UEFI+grub2 on custom focal image with ds=nocloud;s=/cdrom https://bugs.launchpad.net/subiquity/+bug/1878066/+attachment/5369989/+files/custom-focal-ds%3Dnocloud-s%3D_cdrom.tar.gz
2020-05-11 23:01:53 Dimitri John Ledkov bug task added cloud-init (Ubuntu)
2020-05-11 23:04:11 Dimitri John Ledkov description Attempting to automate the installation of Ubuntu Server 20.04 on a variety of machines, some that use isolinux and others that require UEFI+grub2. Booting the installer works fine on all machines tested, but adding ds=nocloud;s=<path-to-file> and ds=nocloud-net;s=<url> do not work for machines that boot via UEFI+grub2. These parameters work fine from the same install media on machines that boot via isolinux. For ds=nocloud;s=<path-to-file>, custom ISO images were used. Both adding meta-data and user-data to the cdrom and to installer.squashfs failed under UEFI, and yet both work fine for isolinux. Also, ds=nocloud-net;s=<url> failed under UEFI for both the custom ISO images and for the standard images. Both the release version of 20.04 and the latest groovy daily build from 2020-05-11 were tested. For test machines that require UEFI+grub2 automated installation appears to be impossible while using ds=...;s=... options. Install logs attached. Tests were performed by inserting an early command: "echo EARLY COMMANDS" into user-data and then checking the log files for the string "EARLY COMMANDS". This proved to be sufficient for testing isolinux boots without the need for a complete installation. For s=<url>, log files were checked after networking was established. cloud-init docs are not clear that ';' in kernel cmdline is potentially missmarsed by bootloaders, and thus the values passed to ds= should be ideally escaped like ds='all the settings' because \; to separate key-value pairs can be eaten easily. see the below confusing where most of the cmdline after and including ';' got discarded -- Attempting to automate the installation of Ubuntu Server 20.04 on a variety of machines, some that use isolinux and others that require UEFI+grub2. Booting the installer works fine on all machines tested, but adding ds=nocloud;s=<path-to-file> and ds=nocloud-net;s=<url> do not work for machines that boot via UEFI+grub2. These parameters work fine from the same install media on machines that boot via isolinux. For ds=nocloud;s=<path-to-file>, custom ISO images were used. Both adding meta-data and user-data to the cdrom and to installer.squashfs failed under UEFI, and yet both work fine for isolinux. Also, ds=nocloud-net;s=<url> failed under UEFI for both the custom ISO images and for the standard images. Both the release version of 20.04 and the latest groovy daily build from 2020-05-11 were tested. For test machines that require UEFI+grub2 automated installation appears to be impossible while using ds=...;s=... options. Install logs attached. Tests were performed by inserting an early command: "echo EARLY COMMANDS" into user-data and then checking the log files for the string "EARLY COMMANDS". This proved to be sufficient for testing isolinux boots without the need for a complete installation. For s=<url>, log files were checked after networking was established.
2020-05-12 19:16:05 Dan Watkins cloud-init (Ubuntu): status New Triaged
2020-05-12 19:16:10 Dan Watkins cloud-init (Ubuntu): importance Undecided Medium
2020-06-11 04:17:49 Michael Hudson-Doyle subiquity: status New Invalid
2020-06-11 15:59:50 Chad Smith tags bitesize