lp:~patviafore/livecd-rootfs/+git/livecd-rootfs

Author: David Krauser
Author Date: 2020-07-16 21:13:59 UTC

Fix broken minimal cloud image boot on amd64 (LP: #1920043)

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.

Author: David Krauser
Author Date: 2020-07-16 21:13:59 UTC

Fix broken minimal cloud image boot on amd64 (LP: #1920043)

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.

Author: Pat Viafore
Author Date: 2021-03-16 21:14:53 UTC

Replace the kernel before messing with grub

replacing the kernel will call force_boot_without_initramfs, which we
want to make sure happens before we mess with grub later on in the hook.

Otherwise, grub will try to boot with a label instead of a UUID, and
fail, resuilting in a kernel panic when trying to find the root.

Author: Pat Viafore
Author Date: 2021-03-16 18:12:57 UTC

Make minimal images not boot with initramfs

Author: Pat Viafore
Author Date: 2020-07-22 13:43:11 UTC

Add mechanism to detect initrdless boot fallback

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.

Addresses LP: #1870189

Author: Pat Viafore
Author Date: 2020-12-02 16:16:25 UTC

Add changelog for revert

In Xenial only, there appears to be a packaging problem whwere
grub-*-signed is not included when installing grub-pc and shim-signed.
This breaks SecureBoot

Author: Pat Viafore
Author Date: 2020-11-30 19:43:32 UTC

Updating changelog for previous cherrypick

Author: Pat Viafore
Author Date: 2020-11-30 19:46:38 UTC

Updating changelog for previous cherrypick

Author: Pat Viafore
Author Date: 2020-05-11 17:24:35 UTC

Rename function to be shorter

Author: Pat Viafore
Author Date: 2020-04-10 20:18:14 UTC

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

Author: Pat Viafore
Author Date: 2020-04-10 20:18:14 UTC

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

Author: Pat Viafore
Author Date: 2020-04-10 20:18:14 UTC

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

Author: Pat Viafore
Author Date: 2020-04-10 20:18:14 UTC

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

Author: Pat Viafore
Author Date: 2020-04-10 20:18:14 UTC

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

Author: Pat Viafore
Author Date: 2020-03-17 16:41:09 UTC

Import socket

Author: Pat Viafore
Author Date: 2020-02-28 14:46:07 UTC

Turn on apt retries and disable threading

Author: Pat Viafore
Author Date: 2020-02-27 19:50:36 UTC

Install tcpdump

Author: Pat Viafore
Author Date: 2019-06-11 22:27:20 UTC

Changing series to UNRELEASED

Author: Pat Viafore
Author Date: 2019-06-04 15:26:01 UTC

Add some comments

Author: CloudBuilder
Author Date: 2019-05-23 06:00:05 UTC

Imported 2.586

No reason for CPC update specified.