[Bug 1920955] Re: [FFe] SRU 1.11 tracking bug

[Iain Lane]

Ack, it sounds isolated and safe enough, but watch out for bugs of
course.

** Changed in: ubuntu-image (Ubuntu)
       Status: New => Triaged

** Changed in: ubuntu-image (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-image in Ubuntu.
https://bugs.launchpad.net/bugs/1920955

Title:
  [FFe] SRU 1.11 tracking bug

Status in Ubuntu Image:
  New
Status in ubuntu-image package in Ubuntu:
  Triaged
Status in ubuntu-image source package in Xenial:
  New
Status in ubuntu-image source package in Bionic:
  New
Status in ubuntu-image source package in Focal:
  New
Status in ubuntu-image source package in Groovy:
  New

Bug description:
  New SRU tracking bug (with exception) for ubuntu-image 1.10 in Groovy,
  Focal, Bionic and Xenial + FFe for hirsute.

  See https://wiki.ubuntu.com/UbuntuImageUpdates

  [Impact]

  ubuntu-image 1.11 is a very very very small and minor release. Basically the only real change (and feature) is related to UC20 images, and is:
   * Use "resolved-content" directory provided by newer versions of "snap prepare-image".

  This is a 'safe' change, as it is fairly isolated, only doing
  something new when snap prepare-image supports it.

  Additionally, for all series below groovy, this release also includes a bugfix for:
   * Add a workaround for mkfs.ext4 forcefully sparsifying our classic image swapfile

  This is a critical change to enable proper building of new DTB-model
  images.

  [FFe rationale]

  This lands so late because all the DTB changes in snapd landed late.
  And we need to have these changes in the Ubuntu archive (most
  importantly in focal) because our UC20 image builds are using ubuntu-
  image from the deb (not the snap). Without this, the UC20 images that
  we build will not include the new DTB structure, which enables proper
  DTB handling via the kernel (not the gadget, as done previously).

  The plus side is that this is really basically the only change in
  1.11. I wouldn't even do a release if not for the fact that we want to
  have proper images building for focal.

  [Test Case]

   * Create an image using the official uc18 amd64 model assertion.
  Ensure that the resulting image boots to 'press enter to configure'
  phase.

   * Create an ubuntu-cpc project classic image using a modified amd64
  gadget tree [1] and make sure it boots.

   * Create an image using the official uc20 amd64 model assertion.
  Ensure that the resulting image boots (possible to ping the
  certification team for help).

  [Regression Potential]

   * ubuntu-image may not produce a bootable image

  [1] For example: https://github.com/sil2100/pc-amd64-gadget

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