[Bug 1849472] Re: Bionic raspi3 images should have the same cloud-init datasource setup as eoan

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.525.33

---------------
livecd-rootfs (2.525.33) bionic; urgency=medium

  * Add support for the 'kassel' subflavor of UC18 images. (LP:
#1850674)

livecd-rootfs (2.525.32) bionic; urgency=medium

  * Fix a terrible typo in auto/build that causes all core18 builds to fail on
    this series (LP: #1849343).
  * Backport 999-ubuntu-image-customization.chroot to have a common place for
    our cloud-init datasource.  Add some modifications on top to make sure the
    legacy raspi2 configuration stays the same (LP: #1849472).
  * Backport enabling of adding extra snaps to ubuntu-core images via the
    EXTRA_SNAPS environment (LP: #1849491).

 -- Łukasz 'sil2100' Zemczak <lukasz.zemczak at ubuntu.com>  Wed, 30 Oct
2019 18:09:02 +0100

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

-- 
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/1849472

Title:
  Bionic raspi3 images should have the same cloud-init datasource setup
  as eoan

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

Bug description:
  [Impact]

  In eoan we switched the datasource configuration from shipping the
  NoCloud config on the rootfs to actually doing that in the system-boot
  boot partition. For our images to be consistent throughout various
  supported series, those changes should be backported to bionic. Also,
  since we basically use one gadget tree for all the series, we'd want
  the bionic parts up-to-date in case we introduce breaking changes in
  the gadget.

  [Test Case]

  1. Image build test.
   * Start a bionic-proposed classic raspi3 build
   * Make sure the build succeeds

  2. Test if datasource is correct.
   * Boot up the newly built raspi3 image
   * Make sure that you can log in with the usual default ubuntu/ubuntu user
   * Check that the boot partition (as mounted in /boot/firmware) has the user-data file

  3. Check if raspi2 did not regress.
   * Start a bionic-proposed raspi2 build
   * Make sure the build succeeds
   * Boot the image
   * Make sure you can correctly log in with the default ubuntu/ubuntu user

  [Regression Potential]

  There is a minimal regression potential related to this upload as we
  are introducing a small delta from what we have in eoan. In eoan we
  stopped building raspi2 images completely, but for bionic this
  'variant' is still supported, so first regression potential I see is
  in breaking the default user configuration for those images. Other
  regression potential might be all related to the 999-cpc-fixes hook,
  in case some configuration is not skipped for certain architectures.

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