[Bug 2027826] Re: Mantic Cloud-Images on amd64 Fail To Preseed Snaps

[Steve Langasek]

On Mon, Jul 24, 2023 at 03:06:15PM -0000, John Chittum wrote:
> So it sounds like the "correct" move may be to add snaps directly to
> `cloud-image` seed.

I think calling 'add_task install cloud-image server' from livecd-rootfs is
better than duplicating the list of snaps between the seeds.

> It seems the breaking issue is that while a snap can
> be included in a seed, and germinate does the proper thing, a
> _metapackage_ produced from a seed does not reference any snaps.

Correct, although by definition "add_task" does not refer to a metapackage,
it refers to a "task".  And there is currently no cloud-image metapackage in
the archive.

The cloud-image seed currently refers to the ubuntu-server package as part
of the seed, which is how add_task pulls it in.  If we changed the seed pod
to declare the cloud-image seed has a dependency on the server seed, would
that be enough to make the current livecd-rootfs implementation follow it
for snaps?

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

Title:
  Mantic Cloud-Images on amd64 Fail To Preseed Snaps

Status in cloud-images:
  New
Status in livecd-rootfs package in Ubuntu:
  Confirmed

Bug description:
  Starting on June 19th, Mantic Cloud Images (in development) on amd64
  are failing to pre-seed snaps provided in Seeds. This is observable by
  taking any Mantic Cloud Server (not minimal) image and checking if
  `lxd` is installed.

  Troubleshooting steps so far:

  1. using `ubuntu-bartender`[0] and local checkouts, I bisected
  `livecd-rootfs`, starting from commits before June 19th.
  Unfortunately, due to various other build issues, I was not able to
  successfully find a commit. Commits <= tag 2.849 fail to build, and
  commits after fail to have snaps preseeded. More work can be done here
  to find a successfully building commit (I did not go a back through
  the entire history, only to tag 2.848)

  2. I attempted a revert of tag 2.890 specific code, which landed
  around the time failures to pre-seed began. Reverting that specific
  code did not result in fixing the issue.

  3. a build and check of the log at `lb_chroot_cache save` will show
  the issue. in a successful build, the apt cache is updated and snaps
  are preseeded.


  [0] https://github.com/ubuntu-bartenders/ubuntu-old-fashioned

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2027826/+subscriptions