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

Bug #1849472 reported by Łukasz Zemczak
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
livecd-rootfs (Ubuntu)
Fix Released
Medium
Łukasz Zemczak
Bionic
Fix Released
Undecided
Łukasz Zemczak

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.

Changed in livecd-rootfs (Ubuntu Bionic):
assignee: nobody → Łukasz Zemczak (sil2100)
status: New → In Progress
Changed in livecd-rootfs (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Adam Conrad (adconrad) wrote : Please test proposed package

Hello Łukasz, 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.33 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: In Progress → Fix Committed
tags: added: verification-needed verification-needed-bionic
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Dave confirmed that the latest bionic daily images (which have -proposed enabled) boot successfully:
 * The raspi3+armhf image works on the pi3 with the default ubuntu/ubuntu credentials
 * The raspi2+armhf legacy image works on the pi2 with the default ubuntu/ubuntu credentials

I am considering this bug verified.

tags: added: verification-done verification-done-bionic
removed: verification-needed verification-needed-bionic
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Wed, 30 Oct 2019 18:09:02 +0100

Changed in livecd-rootfs (Ubuntu Bionic):
status: Fix Committed → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote : Update Released

The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.