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

Owned by Philip Roche
Get this repository:
git clone https://git.not.enabled/~philroche/livecd-rootfs/+git/livecd-rootfs
Only Philip Roche can upload to this repository. If you are Philip Roche please log in for upload directions.

Branches

Name Last Modified Last Commit
bugfix/ubuntu-cpc-LP-2036195-auto-installed-packages-xenial 2023-10-19 17:27:20 UTC
The chroot tmpfs mount should only be /var/lib/apt/lists, not /var/lib/apt; t...

Author: Steve Langasek
Author Date: 2023-09-17 00:27:45 UTC

The chroot tmpfs mount should only be /var/lib/apt/lists, not /var/lib/apt; the latter breaks changes to /var/lib/apt/extended_states. LP: #2036195.

(cherry picked from commit 1deccc2edd7f139b84a6cb3d0a4dfe5ebaff50c7)

# Conflicts:
# debian/changelog

bugfix/ubuntu-cpc-LP-2036195-auto-installed-packages-bionic 2023-10-19 17:21:14 UTC
The chroot tmpfs mount should only be /var/lib/apt/lists, not /var/lib/apt; t...

Author: Steve Langasek
Author Date: 2023-09-17 00:27:45 UTC

The chroot tmpfs mount should only be /var/lib/apt/lists, not /var/lib/apt; the latter breaks changes to /var/lib/apt/extended_states. LP: #2036195.

(cherry picked from commit 1deccc2edd7f139b84a6cb3d0a4dfe5ebaff50c7)

# Conflicts:
# debian/changelog

bugfix/ubuntu-cpc-LP-2036195-auto-installed-packages-focal 2023-10-19 17:17:46 UTC
The chroot tmpfs mount should only be /var/lib/apt/lists, not /var/lib/apt; t...

Author: Steve Langasek
Author Date: 2023-09-17 00:27:45 UTC

The chroot tmpfs mount should only be /var/lib/apt/lists, not /var/lib/apt; the latter breaks changes to /var/lib/apt/extended_states. LP: #2036195.

(cherry picked from commit 1deccc2edd7f139b84a6cb3d0a4dfe5ebaff50c7)

# Conflicts:
# debian/changelog

bugfix/ubuntu-cpc-LP-2036195-auto-installed-packages-lunar 2023-10-19 17:14:09 UTC
The chroot tmpfs mount should only be /var/lib/apt/lists, not /var/lib/apt; t...

Author: Steve Langasek
Author Date: 2023-09-17 00:27:45 UTC

The chroot tmpfs mount should only be /var/lib/apt/lists, not /var/lib/apt; the latter breaks changes to /var/lib/apt/extended_states. LP: #2036195.

(cherry picked from commit 1deccc2edd7f139b84a6cb3d0a4dfe5ebaff50c7)

# Conflicts:
# debian/changelog

bugfix/ubuntu-cpc-LP-2036195-auto-installed-packages-jammy 2023-10-19 17:11:54 UTC
The chroot tmpfs mount should only be /var/lib/apt/lists, not /var/lib/apt; t...

Author: Steve Langasek
Author Date: 2023-09-17 00:27:45 UTC

The chroot tmpfs mount should only be /var/lib/apt/lists, not /var/lib/apt; the latter breaks changes to /var/lib/apt/extended_states. LP: #2036195.

(cherry picked from commit 1deccc2edd7f139b84a6cb3d0a4dfe5ebaff50c7)

# Conflicts:
# debian/changelog

bugfix/ubuntu-cpc-LP-2038957-ppc64el-vmlinux-jammy 2023-10-19 15:30:42 UTC
fix: Enable snap preseeding with ppc64el images where /boot/vmlinux is used i...

Author: Philip Roche
Author Date: 2023-10-11 10:45:29 UTC

fix: Enable snap preseeding with ppc64el images where /boot/vmlinux is used instead of /boot/vmlinuz. (LP: #2038957)

ppc64el still uses /boot/vmlinux so we need to determine the boot file name as non ppc64el use /boot/vmlinuz. This
is then used to determine the kernel major minor version installed so that the correct apparmor features can be used
during snap preseeding. This preseeding was failing for ppc64el for the mantic 6.5 kernel as the /boot/vmlinuz
being checked did not exist.

(cherry picked from commit 089646a32f927f32e9e8961e231391f0bcb6f66b)

# Conflicts:
# debian/changelog
# live-build/functions

bugfix/ubuntu-cpc-LP-2038957-ppc64el-vmlinux 2023-10-19 14:56:51 UTC
fix: Enable snap preseeding with ppc64el images where /boot/vmlinux is used i...

Author: Philip Roche
Author Date: 2023-10-11 10:45:29 UTC

fix: Enable snap preseeding with ppc64el images where /boot/vmlinux is used instead of /boot/vmlinuz. (LP: #2038957)

ppc64el still uses /boot/vmlinux so we need to determine the boot file name as non ppc64el use /boot/vmlinuz. This
is then used to determine the kernel major minor version installed so that the correct apparmor features can be used
during snap preseeding. This preseeding was failing for ppc64el for the mantic 6.5 kernel as the /boot/vmlinuz
being checked did not exist.

bugfix/ubuntu-cpc-LP-2038957-ppc64el-vmlinux-mantic 2023-10-11 10:45:36 UTC
fix: Enable snap preseeding with ppc64el images where /boot/vmlinux is used i...

Author: Philip Roche
Author Date: 2023-10-11 10:45:29 UTC

fix: Enable snap preseeding with ppc64el images where /boot/vmlinux is used instead of /boot/vmlinuz. (LP: #2038957)

ppc64el still uses /boot/vmlinux so we need to determine the boot file name as non ppc64el use /boot/vmlinuz. This
is then used to determine the kernel major minor version installed so that the correct apparmor features can be used
during snap preseeding. This preseeding was failing for ppc64el for the mantic 6.5 kernel as the /boot/vmlinuz
being checked did not exist.

bugfix/ubuntu-cpc-custom-maas 2023-10-06 17:11:01 UTC
custom root squashfs to install util-linux

Author: Philip Roche
Author Date: 2023-10-06 17:11:01 UTC

custom root squashfs to install util-linux

bugfix/ubuntu-cpc-LP-2031921-qcow2-lxd-agent-loader 2023-10-02 11:25:18 UTC
fix: Only install lxd-agent-loader package in ubuntu-cpc qcow2 cloud images (...

Author: Philip Roche
Author Date: 2023-10-02 10:50:30 UTC

fix: Only install lxd-agent-loader package in ubuntu-cpc qcow2 cloud images (LP: #2031921)

There are some packages that are not installed by default in the
disk-image that this binary is based on as the disk-image is used as
a base for all the derivatives. We should keep the number of packages
installed in the disk images that are not applicable to all derivatives to a
minimum and only install packages in images where they are required.
An example of one such package is lxd-agent-loader which
is only applicable to the qcow2 download images which are used for LXD VMs
via simplestreams. This specific example has details in LP#2031921.

This also sets -u to catch any unset variables now that this binary hook is
calling shared functions. One such variable was IMAGE_STR which is used in
the image mounting function `mount_disk_image`

bugfix/ubuntu-cpc-LP-2037074-flashkernel-removal 2023-09-27 10:36:51 UTC
fix: arm flash-kernel removal from ubuntu-cpc project cloud images (LP: #2037...

Author: Philip Roche
Author Date: 2023-09-27 10:33:54 UTC

fix: arm flash-kernel removal from ubuntu-cpc project cloud images (LP: #2037074)

With the migration from linux-kvm to linux-virtual/generic for the mantic minimal
images we can now start building arm64 minimal cloud images.

When building initial test images we noticed that the flash-kernel package was being
installed. This is not required for EFI images.

This commit removes the flash-kernel package from the cloud images arm installs

The only images built using the livecd-rootfs ubuntu-cpc project for arm64 and armhf
which are not cloud images (which therefore do not require flash-kernel) are the
raspi images. raspi does require flash-kernel. But the raspi images use the
`ubuntu-server-raspi` task to install the flash-kernel. As such this non raspi
flash-kernel package install can be completely removed.

It also means that initramfs-tools and dracut-install are installed as these are dependencies
of flash-kernel package.

bugfix/ubuntu-cpc-LP-2037075-minimized-no-recommends 2023-09-26 17:08:09 UTC
fix: Ensure that grub/shim package installs do not install recommends for min...

Author: Philip Roche
Author Date: 2023-09-26 16:28:25 UTC

fix: Ensure that grub/shim package installs do not install recommends for minimized ubuntu-cpc image builds (LP: #2037075)

minimized cloud image policy, introduced in version 23.10.16, is to not install recommends for any package
installs during build. This is to keep the image as small as possible. This also extends to
the grub related packages.

This solves the problems detailed in LP: #2037075 and aligns other arches more with amd64 install of
grub/shim packages for both minimized and non minimized ubuntu-cpc cloud image builds.

bugfix/ubuntu-cpc-LP-2037074-flashkernel 2023-09-22 11:31:27 UTC
fix: arm flash-kernel removal from minimal cloud images (ubuntu-cpc project) ...

Author: Philip Roche
Author Date: 2023-09-22 11:28:18 UTC

fix: arm flash-kernel removal from minimal cloud images (ubuntu-cpc project) (LP: #2037074)

With the migration from linux-kvm to linux-virtual/generic for the mantic minimal
images we can now start building arm64 minimal cloud images.

When building initial test images we noticed that the flash-kernel package was being
installed. This is not required for EFI images.

This commit removes the flash-kernel package from the minimal cloud images arm installs

It also means that initramfs-tools and dracut-install are installed as these are dependencies
of flash-kernel package.

bugfix/ubuntu-cpc-LP-2037075-efibootmgr 2023-09-22 11:16:08 UTC
fix: Install with recommends when installing grub/shim packages in arm ubuntu...

Author: Philip Roche
Author Date: 2023-09-22 10:59:00 UTC

fix: Install with recommends when installing grub/shim packages in arm ubuntu-cpc minimized images (LP: #2037075)

With the migration from linux-kvm to linux-virtual/genreic for the mantic minimal
images we can now start building arm64 minimal cloud images.

When building initial test images we noticed that when comparing the amd64 minimized images
and the arm64 images that the efibootmgr package was not installed in the arm64 images.

This is because for amd64 it is installed as a recommends of shim-signed but for arm64
we are installing shim-signed `--no-install-recommends`.

This commit ensures that we align more with amd64 install of grub/shim packages for arm
images and also install recommends packages.

For arm64 this ensures that efibootmgr is installed too.

bugfix/ubuntu-cpc-unminimize-syntax-error 2023-09-19 16:03:50 UTC
Update d/ch for 23.10.42 release

Author: Philip Roche
Author Date: 2023-09-19 10:30:40 UTC

Update d/ch for 23.10.42 release

bugfix/ubuntu-cpc-LP-2036192-armhf 2023-09-15 11:00:15 UTC
fix: armhf flavour for 6.5+ kernel is now generic (LP: #2033677)

Author: Philip Roche
Author Date: 2023-09-15 10:36:26 UTC

fix: armhf flavour for 6.5+ kernel is now generic (LP: #2033677)

With the introduction of the 6.5 kernel for mantic on 13th September ago we are seeing image build failures
on the armhf builds. The build failure was `No kernel output for generic-lpae!`.

Introduced in the 6.4 kernel and therefore now also in 6.5 there is no generic-lpae flavor anymore. it's just generic now.

As such this commit updates the expected flavour for armhf to generic.

bugfix/minimize-manual-LP-2036198 2023-09-15 10:59:12 UTC
fix: ensure minimize-manual script uses passed in argument for all commands (...

Author: Philip Roche
Author Date: 2023-09-15 10:59:06 UTC

fix: ensure minimize-manual script uses passed in argument for all commands (LP: #2036198)

minimize-manual takes an argument of the path to the chroot but of the 3 commands that are run the argument
is only used twice and with the third hardcoding "chroot" as the path to the chroot.

Thankfully "chroot" has been the patch passed in for the current uses of minimize-manual but this
could cause issues later if that were to change.

This commit resolves the problem preventing future issues.

bugfix/ubuntu-cpc-project-images-not-producing-all-expected-filelists-LP-2033751 2023-09-01 11:24:59 UTC
Update changelog for livecd-rootfs 23.10.31 (LP: #2033751)

Author: Philip Roche
Author Date: 2023-09-01 11:24:59 UTC

Update changelog for livecd-rootfs 23.10.31 (LP: #2033751)

mantic 2023-09-01 00:51:14 UTC
Imported 23.10.29 from mantic-release pocket.

Author: Philip Roche
Author Date: 2023-09-01 00:51:14 UTC

Imported 23.10.29 from mantic-release pocket.

No reason for CPC update specified.

bugfix/ubuntu-cpc-filelist-sort-LP-2033677 2023-08-31 19:36:00 UTC
fix: Sort filelists creating when building ubuntu-cpc images (LP: #2033677)

Author: Philip Roche
Author Date: 2023-08-31 17:26:42 UTC

fix: Sort filelists creating when building ubuntu-cpc images (LP: #2033677)

The image filelists created during ubuntu-cpc project image builds were not sorted.

Soring the filelists makes it easier to compare the filelists without needing to sort first.

bugfix/ubuntu-cpc-minimized-no-install-recommends-upstream-master 2023-08-17 11:41:46 UTC
fix: Only close LP bug once in changelog entry

Author: Philip Roche
Author Date: 2023-08-17 11:41:46 UTC

fix: Only close LP bug once in changelog entry

Indent related fixes under same bug heading

bugfix/ubuntu-cpc-minimized-no-install-recommends 2023-08-11 12:46:40 UTC
fix: Install required package fuse3 when preseeding snaps

Author: Philip Roche
Author Date: 2023-08-11 12:46:40 UTC

fix: Install required package fuse3 when preseeding snaps

fuse3 was previously installed through recommends but with minimized images we no longer install recommends packages.

It is only required when preseeding snaps so does not need to be present in all minimized images so does not
need to be in the cloud-minimal seed.

hotfix/rebuild-lunar 2023-05-08 15:01:28 UTC
fix: Continue to build lunar with CPC fork until upstream upate the lunar rel...

Author: Philip Roche
Author Date: 2023-05-08 15:01:19 UTC

fix: Continue to build lunar with CPC fork until upstream upate the lunar release of livecd-rootfs

An ubuntu/lunar upstream git branch is also required

hotfix/rebuild-mantic 2023-05-08 14:54:02 UTC
fix: Continue to build mantic with CPC fork until upstream push a mantic rele...

Author: Philip Roche
Author Date: 2023-05-08 14:43:15 UTC

fix: Continue to build mantic with CPC fork until upstream push a mantic release of livecd-rootfs

hotfix/snapd-preseeding-use-chroot-preseed-focal 2023-01-13 13:25:41 UTC
fix: use chroot preseed

Author: Philip Roche
Author Date: 2023-01-13 13:25:41 UTC

fix: use chroot preseed

hotfix/snapd-preseeding-channel-pin-lunar 2023-01-13 09:40:12 UTC
fix: Temporarily pin snapd preseeding to snap channel stable/2.57.x

Author: Philip Roche
Author Date: 2023-01-13 09:40:12 UTC

fix: Temporarily pin snapd preseeding to snap channel stable/2.57.x

There is a regression in snapd 2.58 with a fix being worked on @
https://github.com/snapcore/snapd/pull/12483. The regression was
that it was no longer possible to preseed snaps during cloud
image builds. The temporary workaround is to preseed snapd
from a downgraded channel "stable/2.57.x". To do this temporarily
we will carry a patch on CPC's fork of livecd-rootfs on all suites.

Once the fix to snapd snap is rolled out with a new 2.58.1
release then the "stable/2.57.x" will be removed and
all users with snapd from channel "stable/2.57.x" will
fall back to "stable" channel and be upgraded to 2.58.1.

hotfix/snapd-preseeding-channel-pin-kinetic 2023-01-13 09:39:03 UTC
fix: Temporarily pin snapd preseeding to snap channel stable/2.57.x

Author: Philip Roche
Author Date: 2023-01-13 09:39:03 UTC

fix: Temporarily pin snapd preseeding to snap channel stable/2.57.x

There is a regression in snapd 2.58 with a fix being worked on @
https://github.com/snapcore/snapd/pull/12483. The regression was
that it was no longer possible to preseed snaps during cloud
image builds. The temporary workaround is to preseed snapd
from a downgraded channel "stable/2.57.x". To do this temporarily
we will carry a patch on CPC's fork of livecd-rootfs on all suites.

Once the fix to snapd snap is rolled out with a new 2.58.1
release then the "stable/2.57.x" will be removed and
all users with snapd from channel "stable/2.57.x" will
fall back to "stable" channel and be upgraded to 2.58.1.

hotfix/snapd-preseeding-channel-pin-xenial 2023-01-13 09:37:41 UTC
fix: Temporarily pin snapd preseeding to snap channel stable/2.57.x

Author: Philip Roche
Author Date: 2023-01-13 09:37:41 UTC

fix: Temporarily pin snapd preseeding to snap channel stable/2.57.x

There is a regression in snapd 2.58 with a fix being worked on @
https://github.com/snapcore/snapd/pull/12483. The regression was
that it was no longer possible to preseed snaps during cloud
image builds. The temporary workaround is to preseed snapd
from a downgraded channel "stable/2.57.x". To do this temporarily
we will carry a patch on CPC's fork of livecd-rootfs on all suites.

Once the fix to snapd snap is rolled out with a new 2.58.1
release then the "stable/2.57.x" will be removed and
all users with snapd from channel "stable/2.57.x" will
fall back to "stable" channel and be upgraded to 2.58.1.

hotfix/snapd-preseeding-channel-pin-bionic 2023-01-13 09:36:32 UTC
fix: Temporarily pin snapd preseeding to snap channel stable/2.57.x

Author: Philip Roche
Author Date: 2023-01-13 09:36:32 UTC

fix: Temporarily pin snapd preseeding to snap channel stable/2.57.x

There is a regression in snapd 2.58 with a fix being worked on @
https://github.com/snapcore/snapd/pull/12483. The regression was
that it was no longer possible to preseed snaps during cloud
image builds. The temporary workaround is to preseed snapd
from a downgraded channel "stable/2.57.x". To do this temporarily
we will carry a patch on CPC's fork of livecd-rootfs on all suites.

Once the fix to snapd snap is rolled out with a new 2.58.1
release then the "stable/2.57.x" will be removed and
all users with snapd from channel "stable/2.57.x" will
fall back to "stable" channel and be upgraded to 2.58.1.

hotfix/snapd-preseeding-channel-pin-jammy 2023-01-13 09:33:24 UTC
fix: Temporarily pin snapd preseeding to snap channel stable/2.57.x

Author: Philip Roche
Author Date: 2023-01-13 09:33:24 UTC

fix: Temporarily pin snapd preseeding to snap channel stable/2.57.x

There is a regression in snapd 2.58 with a fix being worked on @
https://github.com/snapcore/snapd/pull/12483. The regression was
that it was no longer possible to preseed snaps during cloud
image builds. The temporary workaround is to preseed snapd
from a downgraded channel "stable/2.57.x". To do this temporarily
we will carry a patch on CPC's fork of livecd-rootfs on all suites.

Once the fix to snapd snap is rolled out with a new 2.58.1
release then the "stable/2.57.x" will be removed and
all users with snapd from channel "stable/2.57.x" will
fall back to "stable" channel and be upgraded to 2.58.1.

hotfix/snapd-preseeding-channel-pin-focal 2023-01-13 09:31:36 UTC
fix: Temporarily pin snapd preseeding to snap channel stable/2.57.x

Author: Philip Roche
Author Date: 2023-01-13 09:31:36 UTC

fix: Temporarily pin snapd preseeding to snap channel stable/2.57.x

There is a regression in snapd 2.58 with a fix being worked on @
https://github.com/snapcore/snapd/pull/12483. The regression was
that it was no longer possible to preseed snaps during cloud
image builds. The temporary workaround is to preseed snapd
from a downgraded channel "stable/2.57.x". To do this temporarily
we will carry a patch on CPC's fork of livecd-rootfs on all suites.

Once the fix to snapd snap is rolled out with a new 2.58.1
release then the "stable/2.57.x" will be removed and
all users with snapd from channel "stable/2.57.x" will
fall back to "stable" channel and be upgraded to 2.58.1.

hotfix/snapd-preseeding-channel-pin-revert-lunar 2023-01-11 04:48:18 UTC
Imported 2.796

Author: CloudBuilder
Author Date: 2023-01-11 04:48:18 UTC

Imported 2.796

No reason for CPC update specified.

feature/ubuntu-impish-fix-armhf-disk-image-size-bug-1953609 2021-12-08 12:01:01 UTC
Bump UEFI disk image size for armhf to 3.5 GB LP:#1953609

Author: Philip Roche
Author Date: 2021-12-08 11:25:46 UTC

Bump UEFI disk image size for armhf to 3.5 GB LP:#1953609

Current impish builds fail with:
```
cp: error writing 'mountpoint/var/lib/snapd/snaps/snapd_14067.snap': No space left on device
cp: cannot create directory 'mountpoint/var/lib/snapd/ssl': No space left on device
```

This is a cherrypick backport from ubuntu/master

feature/impish-fix-armhf-disk-image-size 2021-12-08 09:39:06 UTC
Bump UEFI disk image size for armhf to 3.5 GB

Author: Philip Roche
Author Date: 2021-12-08 09:19:48 UTC

Bump UEFI disk image size for armhf to 3.5 GB

Current impish builds fail with:
```
cp: error writing 'mountpoint/var/lib/snapd/snaps/snapd_14067.snap': No space left on device
cp: cannot create directory 'mountpoint/var/lib/snapd/ssl': No space left on device
```

This is a cherry pick backport from jammy

sru/revert-initramfs-tools-removal-focal 2020-05-22 12:38:22 UTC
Revert of initramfs package removal in KVM image (LP: #1880170)

Author: Philip Roche
Author Date: 2020-05-18 16:06:08 UTC

Revert of initramfs package removal in KVM image (LP: #1880170)

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: #1880170

sru/revert-initramfs-tools-removal-eoan 2020-05-22 12:37:22 UTC
Revert of initramfs package removal in KVM image (LP: #1880170)

Author: Philip Roche
Author Date: 2020-05-22 12:37:22 UTC

Revert of initramfs package removal in KVM image (LP: #1880170)

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: #1880170

bugfix/revert-initramfs-tools-removal 2020-05-18 16:08:30 UTC
Revert of initramfs package removal in KVM image (LP: #1875400)

Author: Philip Roche
Author Date: 2020-05-18 16:06:08 UTC

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

137 of 37 results
This repository contains Public information 
Everyone can see this information.

Subscribers