[Bug 2007419] Re: buildd daily kinetic, lunar, and mantic image missing systemd-resolved
Timo Aaltonen
2007419 at bugs.launchpad.net
Fri Apr 12 18:52:20 UTC 2024
Hello Callahan, or anyone else affected,
Accepted livecd-rootfs into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/23.10.59 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: livecd-rootfs (Ubuntu Mantic)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-mantic
--
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/2007419
Title:
buildd daily kinetic, lunar, and mantic image missing systemd-resolved
Status in cloud-images:
Fix Committed
Status in livecd-rootfs package in Ubuntu:
Fix Released
Status in livecd-rootfs source package in Lunar:
Won't Fix
Status in livecd-rootfs source package in Mantic:
Fix Committed
Bug description:
[ Impact ]
* There was a regression in the buildd images when systemd-resolved was moved
out of systemd to a separate package, as the buildd recipes did not include
systemd-resolved. Those images don't include a resolvconf anymore.
* This affects buildd images only in the context where they are booted
standalone (e.g. kvm, multipass). buildd containers which get network
configuration injected (like launchpad) are not affected.
* This fix adds the systemd-resolved package explicitly, making the resolver
available on buildd images like pre-kinetic.
[ Test Plan ]
* Build image with project=ubuntu-base subproject=buildd
image_target=all
* Boot qcow2 buildd image. run `apt-get update`
* Apt should be able to resolve mirrors and update fine.
[ Where problems could occur ]
* If the context in which buildd images are used injects a resolv.conf
without unlinking the systemd-resolved stub, the resolver might revert
the injected config to the systemd-resolved stub on restart.
[ Original Description ]
Hello,
I'm trying to use the buildd daily images [1]. However, I'm having an
issue with `systemd-resolved` not being installed on buildd's daily
kinetic and lunar images.
From what I can gather, systemd-resolved:
1. exists in all other buildd daily images and buildd release images
2. exists in the other cloud images [2]
3. was separated from the systemd package in kinetic and lunar [3]
It's a bit of a catch-22, because without `systemd-resolved` or
literally `/usr/bin/resolvectl`, I can't run `apt install systemd-
resolved` in my LXD environment.
Can someone please advise? Was this package excluded on purpose?
Sources:
[1] https://cloud-images.ubuntu.com/buildd/daily/
[2] https://cloud-images.ubuntu.com/
[3] https://packages.ubuntu.com/search?keywords=systemd-resolved&searchon=names&exact=1&suite=all§ion=all
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2007419/+subscriptions
More information about the foundations-bugs
mailing list