[Bug 2027826] Re: Mantic Cloud-Images on amd64 Fail To Preseed Snaps
Michael Hudson-Doyle
2027826 at bugs.launchpad.net
Wed Jul 26 22:50:46 UTC 2023
On Thu, 27 Jul 2023 at 03:55, Steve Langasek <2027826 at bugs.launchpad.net>
wrote:
> > pardon my ignorance, but is that done in the STRUCTURE file?
>
> That was what I had in mind, but the implementation says:
>
Yeah, the STRUCTURE file is actually kind of the opposite of a dependency:
if STRUCTURE says seed2: seed1 then the package list for seed2 will not
include any packages that are in seed1! The use case for this is package
pools on ISOs, for example the declaration
server-ship-live: server-minimal
Means that we do not end up with any packages in the pool that are always
going to be installed in the target system anyway.
I had forgotten / failed to find the task-seed header which was one of the
reasons I hadn't gotten around to replying to this bug!
This is all a big mess yes.
--
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:
Fix Released
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
More information about the foundations-bugs
mailing list