86 Commits (0fa7ab23ed0c8fbf46f64541243903ec520e91d1)

Author	SHA1	Message	Date
John Chittum	c92e885303	ubuntu-cpc: Vagrant Serial to Null (LP: #1874453) ... Original fix proposed by Stanislav German-Evtushenko (giner) CPC Ubuntu cloud images default to enabling a serial console connection via the kernel commandline option `console=ttyS0`. Many clouds support the serial connection, and utilize it for debugging purposes. Virtualbox supports the serial connection as well. In Bionic and earlier images, Vagrant boxes created a serial log file in the directory of the Vagrantfile by default. However this is not standard behaviour for Vagrant images, and so it was removed in Eoan onwards. Starting in Eoan, there were reports of image booting slowdown (1874453 is a single example). After testing, it was determined that the serial connection starting, without a device attached, was the cause of the slow down. However, we did not want to revert to the old functionality of creating a file. Much thanks to <giner> for providing the Ruby syntax for sending to File::NULL. This option will not create a local file, however, the default Vagrantfile configuration is overwritable via a users Vagrantfile. The original syntax for creating a file local to the users Vagrantfile has been included as an example.	4 years ago
Stanislav German-Evtushenko	b0144d3018	vagrant: Use dummy file for the console output ... Links: - https://bugs.launchpad.net/cloud-images/+bug/1874453	4 years ago
Steve Langasek	37f5f8881f	Revert "Revert "Remove fstab from squashfs images"" ... This reverts commit d9de270189.	4 years ago
Robert C Jennings	2844aa530d	Revert ubuntu-cpc: Disable boot splash ... These introduced a regression for ppc64el and needs more time to bake. This reverts commits 1deb0c68e8 & 6dbb30f53b. * "ubuntu-cpc: Fix ppc64el grub console update" * "ubuntu-cpc: Disable boot splash in all cloud images (LP: #1725358)"	4 years ago
Robert C Jennings	1deb0c68e8	ubuntu-cpc: Fix ppc64el grub console update ... The commit 6dbb30f5 (2.682) which disabled boot splash for all cloud images introduced an error in the ppc64el hook. This patch corrects the name of the variable that contains grub console overrides. The error seen during testing was 'disk-image-ppc64el.binary: line 44: CONSOLES: unbound variable' and this was due to a typo.	4 years ago
Steve Langasek	d9de270189	Revert "Remove fstab from squashfs images" ... This reverts commit f96e874ed1.	4 years ago
Robert C Jennings	6dbb30f53b	ubuntu-cpc: Disable boot splash in all cloud images (LP: #1725358) ... When trying to debug an issue on ARM64 it was reported that it was quite difficult to debug because of control codes on the console from the splash. For cloud image there is a chroot customization the drops 'quiet splash' but this is only applied to amd64. It hasn't made it into other architectures because they don't have grub by default in the chroot. However, when we get into binary hook for the uefi disk image and it's derivatives grub is installed and this includes architectures that were skipped in the chroot hook. This patch changes the cpc-fixes chroot hook to add a cloud-images grub config with basic overrides, including dropping the boot splash, for all architectures. For images that never get grub installed this addition is harmless and small while ensuring that the grub experience is consistent for images that have grub. The configuration of console devices as hard-coded remains arch specific.	4 years ago
David Krauser	83499f1a95	Add mechanism to detect initrdless boot fallback ... In v2.672 the default boot behavior of cloud images changed: - Prior to v2.672, cloud images with the linux-generic kernel attempt to boot without an initramfs, would fail, and then retry with an initramfs. - After v2.672, cloud images with the linux-generic kernel boot with an initramfs on the first try. While the behavior is different between the two, they both result in an instance that has booted with an initramfs. To ensure the changes in v2.672 do not regress, we need an automated way to check if we are attempting to boot without an initramfs and failing. With this change, when we attempt to boot with an initramfs and fail, initrdless_boot_fallback_triggered is set to non-zero in the grubenv. This value can be checked after boot by looking in /boot/grub/grubenv or by using the grub-editenv list command.	4 years ago
David Krauser	4c504f6781	Fix broken minimal cloud image boot on amd64 ... I recently pulled initramfs logic out of the base build hook, and dropped that into the `replace_kernel` function. Any cloud image that does not leverage the generic virtual kernel was expected to call `replace_kernel` to pull in a custom kernel. That function will disable initramfs boot for images that use a custom kernel. Minimal cloud images on amd64 use the linux-kvm kernel, but the build hook does not utilize the `replace_kernel` function. Instead, the kernel flavor is set in `auto/config`. I pulled that logic out of `auto/config` and am now calling `replace_kernel` in the build hook. I also moved a call to generate the package list so that it will pick up the change to the linux-kvm kernel.	5 years ago
David Krauser	e8e3e6760f	Drop hack in kvm image that forces initramfs-less boot ... Since the kvm image now boots without an initramfs by default, we don't need to force it in the build hook.	5 years ago
David Krauser	1ca1330eae	Boot with an initramfs by default in cloud images ... Generic cloud images with the linux-generic kernel are not able to boot without an initramfs. Previously, these images attempted to boot without an initramfs, would fail, and then retry with an initramfs. This slows the boot and is confusing behavior.	5 years ago
Balint Reczey	f96e874ed1	Remove fstab from squashfs images ... The default fstab is not valid, since squashfs does not support labels. LP: #1877078	5 years ago
Philip Roche	60665a434b	Revert of initramfs package removal in KVM image (LP: #1875400) ... It was reported and confirmed in LP bug #1875400 (https://bugs.launchpad.net/cloud-images/+bug/1875400) that on the public KVM cloud image there exists a large list of packages marked for auto-removal. This should never be the case on a released cloud image. These packages are marked for auto-removal because in the KVM image binary hook we removed both initramfs-tools and busybox-initramfs packages. Due to package dependencies this also removed: busybox-initramfs* cloud-initramfs-copymods* cloud-initramfs-dyn-netconf* cryptsetup-initramfs* initramfs-tools* initramfs-tools-core* multipath-tools* overlayroot* sg3-utils-udev* ubuntu-server* But it did not remove all the packages that the above list depended on. This resulted in all those packages being marked for auto-removal because they were not manually installed nor did they have any manually installed packages that depended on them. The removal of initramfs-tools and busybox-initramfs was to avoid the generation of initramfs in images that should boot initramfsless. This requirement is obsolete now because the initramfsless boot handling is now handled via setting GRUB_FORCE_PARTUUID in /etc/default/grub.d/40-force-partuuid.cfg. In test images I have verified that GRUB_FORCE_PARTUUID is set and that boot speeds have not regressed. LP: #1875400	5 years ago
Pat Viafore	2c70ed158b	Make Ubuntu Vagrant box 40G. (LP: #1580596) ... Vagrant images were previously put at 10G, but this was a regression from Trusty, in which they were 40G. This made it a tough sell for users to upgrade if they were using a Ubuntu desktop experience. This change does not impact disk usage as Vagrant with the virtualbox provider dynamically allocates space with the VMDK. On a test system, the VMDK took up 1.1G of disk space according to df, and after creating a 2G file in Vagrant, the VMDK grew to 3.1G. Therefore, users who are running on a system with little free space will not see adverse effects if they upgrade to a new vagrant image	5 years ago
Michael Hudson-Doyle	741933942e	copy the filelists for the root-xz and squashfs into place	5 years ago
Michael Hudson-Doyle	015d8bab65	add filelist files to all ubuntu-cpc series files	5 years ago
Dimitri John Ledkov	584ac368b0	Merge branch 'kvm-derives-uefi' of git+ssh://git.launchpad.net/~davidkrauser/livecd-rootfs/+git/livecd-rootfs into ubuntu/master	5 years ago
David Krauser	0eecd0c344	KVM disk images should derive from the uefi image.	6 years ago
Robert C Jennings	cb535805d7	ubuntu-cpc: rework image artifact cleanup ... The livecd.ubuntu-cpc.ext4 that is present in each build (plus kernel and initrd) are not renamed from /build/binary/boot/filsystem.ext4 and friends until after the binary hooks are run, so this patch moves from trying to perform this cleanup in a binary hook. Now the cleanup will be run at the end of live-build/binary for the ubuntu-cpc project.	6 years ago
Robert C Jennings	14b7f62b17	ubuntu-cpc: Only produce explicitly named artifacts (LP: #1837254) ... In parallel builds where a list of image targets are provided the build may produce binaries that are not part of the named set of targets but are created by series dependencies. These implicitly created binaries may be generated by multiple builds but are unused as our convention for the ubuntu-cpc project is to only consume binaries from the explicitly named image targets; this avoid overwriting the same object by multiple parallel builds. This patch adds support for a 'provides' keyword for series files. It can be specified multiple times per series file. The field is used by the make-hooks script to generate a list of output files created explicitly by the named image targets. The list is saved to the "explicit_provides" file in the hooks output directory. In the case of the "all" target this list would be empty. This list is consumed by the "final.binary" hook file. This patch adds support for optional final.binary hooks in hooks.d/base and/or hooks.d/extra. These final.binary hooks are always included as the last hook(s) if either exist with the hook in "extra" running last. The base/final.binary hook includes logic to parse the "explicit_provides" file generated by the make-hooks script and remove any binary output not explicitly specified. Some series files named unnecessary dependencies, specifically disk-image, to keep output of implicit artifacts consistent between parallel builds. These unnecessary dependencies are removed in this patch.	6 years ago
David Krauser	0e3b1e206b	Add support for HyperV Gallery images	6 years ago
Pat Viafore	514a83b926	Unmount the image before we convert to qcow2 to avoid corruption	6 years ago
Pat Viafore	9bf4c7cb52	Adding apt-get autoremove and setting IMAGE_STR	6 years ago
Pat Viafore	975a620e59	Various fixes from code review. ... Cleaning indices; removing superfluous apt-get update; adding debug messages; adding better output name	6 years ago
Pat Viafore	afbda566eb	Adding hooks and making replace_kernel function	6 years ago
Pat Viafore	528b2ea57a	Add kvm image	6 years ago
Balint Reczey	76a57f37ef	Merge lp:~rbalint -b ubuntu/master	6 years ago
Michael Hudson-Doyle	d35d115938	Merge branch 'ubuntu/master_parallel_cpc_fixes' into ubuntu/master	6 years ago
Balint Reczey	2bb15e03f4	wsl.binary: Add comment about tar usage	6 years ago
Balint Reczey	3ae9628528	Build WSL rootfs tarball ... LP: #1827930	6 years ago
Robert C Jennings	bca9242474	ubuntu-cpc: Allow comments in series files and add comments ... The addition of disk-image to series files in a prior commit required some explanation. Without comment support in series files that was not possible. This patch adds support for comments and adds those comments as well.	6 years ago
Robert C Jennings	05850394d7	ubuntu-cpc: Ensure base disk image is the same between all build targets ... The following targets have livecd.ubuntu-cpc.manifest (and livecd.ubuntu-cpc.ext4) which differ in some way from the 'all' target. They are all missing grub-efi and other modifications: root-dir squashfs tarball These targets do not depend on the 'disk-image' target. This means that the ext4 produced will lack the uefi modifications (and any from the disk-image target binary hooks). Since the ext4 file is common to all builds there is a chance that a parallel build from one of these targets could overwrite this artifact. This patch ensures that all targets will produce consistent base output.	6 years ago
Robert C Jennings	0bfc5c4290	ubuntu-cpc: Fixup comment references to file names post-parallelization	6 years ago
Balint Reczey	2d162dd121	Pass --sort=name to tar to make tarballs more reproducible and rsync-friendly	6 years ago
Robert C Jennings	a45342f269	ubuntu-cpc: avoid duplicate snaps listed in qcow manifest ... commit a993592 introduced an additional call to create_manifest (and snap-seed-parse) to write binary/boot/filesystem.packages. This caused duplicate snap lines in the qcow manifest. This is because the live-build/auto/binary code assumes that after 'lb binary' is run the filesystem.packages will only have debs and it calls snap-seed-parse to add them to the file. The commit changed filesystem.packages in the ubuntu-cpc uefi binary hook to include debs and snaps. This patch keeps the intent of the prior patch, updating the filesystem.packages file for the content of the uefi disk image, but only writes a listing of debian packages to match the expected content of filesystem.packages. The snaps will still be added in generic code in live-build/auto/build.	6 years ago
Tobias Koch	cbd4eb5717	Use series files with dependency handling to generate hook symlinks dynamically ... This patch currently only applies to the "ubuntu-cpc" project. More and more logic has been going into the hook scripts to decide under which conditions they should run or not. As we are moving to parallelized builds of image sets, this will get even more complicated. Base hooks will have to know which image sets they belong to and modification of the dependency chain between scripts will become more complicated and prone to errors, as the number of image sets grows. This patch introduces explicit ordering and dependency handling for scripts through the use of `series` files and an explicit syntax for dependency specification.	6 years ago