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

[Simon Poirier]

> pardon my ignorance, but is that done in the STRUCTURE file?
> So we'd add the dependency thusly?
>
> cloud-image: standard server

negative. The structure from germinate output appears completely ignored
(except checking its presence) by add_task, and seeds appear to only be
expanded if added explicitly. The cloud-image seed depends on ubuntu-
server so happens to have most of the seed (minus the snaps) without
previously having it added explicitly.

For fixing the current issue, adding the server task where we add cloud-
image would do the trick (we almost do it for all archs; see linked
branch)

For the longer term, I think it would make sense to actually walk the
germinate structure and recursively add tasks. I've tested that but I'm
unsure of the implications of such a change, apart from also having
minimized point to cloud-minimal instead of cloud-image.


** Changed in: cloud-images
       Status: New => In Progress

-- 
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:
  In Progress
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