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

[Steve Langasek]

> pardon my ignorance, but is that done in the STRUCTURE file?

That was what I had in mind, but the implementation says:

> def getTaskSeeds(task_headers, seedname):
>     """Return the list of seeds used to generate a task from this seed.
> 
>     The list of packages in this task comes from this seed plus any
>     other seeds listed in a Task-Seeds header.

So I've committed a change to add Task-Seeds: server to the cloud-image
seed.

> setting block-proposed-mantic on this bug report, to prevent livecd-rootfs
> migrating with more changes piled onto it, unless this bug is resolved.

Not an appropriate use of the tag.  The tag is for preventing
regressions from entering the release pocket.  It is not a "stop the
line" marker when you want to escalate that a team should prioritize
fixing a particular issue, and it also does not mean we will revert any
of the already-staged changes in mantic-proposed.

Anyway, the proper fix for this looks to not be in the livecd-rootfs
code at all.  I'm starting a test build now with the seed change and
will report back on the bug.

** Tags removed: block-proposed-mantic
** Tags added: rls-mm-incoming

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