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

[Dan Bungert]

I'm not sure what's going on with the build failures when using
bartender, I wasn't testing in that way.

As for why the cpc builds stopped on the 19th, I do suspect it was my
changes, but Łukasz followed up shortly after with a fix, so I'm not
sure why the builds stopped since then.

For LXD being seeded or not, I traced this to livecd-rootfs 2.837.

* passing build log - lxd seeded - with livecd-rootfs 2.836 equivalent + some "set -x"
https://launchpad.net/~dbungert/+livefs/ubuntu/mantic/test/+build/467075/+files/buildlog_ubuntu_mantic_amd64_test_BUILDING.txt.gz

* failing build log - lxd not seeded - with livecd-rootfs 2.837 equivalent + "set -x"
https://launchpad.net/~dbungert/+livefs/ubuntu/mantic/test/+build/467080/+files/buildlog_ubuntu_mantic_amd64_test_BUILDING.txt.gz

As a result of that change, there is a difference in which seed is
considered (old considered server, new considered cloud-image), but that
difference sounds more correct so I don't want to just revert 2.837.

So for the lxd part of this, I suspect the answer is to seed the lxd
snap in cloud-image, but that sounds like a cpc team call.

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

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