[Bug 1827357] Re: SRU subiquity specific changes from master to bionic

[Brian Murray]

Hello Dimitri, or anyone else affected,

Accepted livecd-rootfs into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.525.23 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: livecd-rootfs (Ubuntu Bionic)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  SRU subiquity specific changes from master to bionic

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * SRU subiquity image specific changes in livecd-rootfs to fix
  installer issues.

  [Test Case]

    * subiquity: make subiquity_config.mount optional.

      1) boot subiquity image
      2) observe that there are no boot messages mentioning failed to start subiquity_config.mount

    * Make serial-subiquity@ use the same codepath as tty1 subiquity.

      1) boot subiquity image on an architecture with a serial console, e.g. ppc64el KVM, s390x KVM.
      2) observe that the boot goes straight to subiquity, without multiple attempts of failing to start it, crash, try again, crash, snaps get seeded, success.

    * Fix ubuntu-server-live images to generate initrd with casper UUID.

      1) mount iso
      2) check that it contains uuid file
      cat /mnt/.disk/casper-uuid-generic
      3) unpack initrd
      unmkinitramfs /mnt/casper/initrd /tmp/tmp.AGwIMQfj0j
      4) check that it also contains uuid:
      cat /tmp/tmp.AGwIMQfj0j/main/conf/uuid.conf
      5) check that uuid form #2 and #4 are the same

  [Regression Potential]

   * This is a livecd-rootfs upload that may impact building images. The
  code touched here affects ubuntu-server-live images only. This SRU
  should be reviewed and accepted, server-live images spun and checked
  as per the above testcases.

  [Other Info]
   
   * All changes are cherrypicks from disco/eoan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1827357/+subscriptions