buildd daily kinetic, lunar, and mantic image missing systemd-resolved
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cloud-images |
In Progress
|
Undecided
|
Simon Poirier | ||
| livecd-rootfs (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
| Lunar |
Confirmed
|
Undecided
|
Unassigned | ||
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-
* 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/
Can someone please advise? Was this package excluded on purpose?
Sources:
[1] https:/
[2] https:/
[3] https:/
Related branches
- Ubuntu Core Development Team: Pending requested
-
Diff: 28 lines (+9/-0)2 files modifieddebian/changelog (+6/-0)
live-build/auto/config (+3/-0)
- Utkarsh Gupta: Needs Fixing
- Canonical Launchpad Engineering: Pending requested
-
Diff: 14 lines (+3/-0)1 file modifiedlive-build/auto/config (+3/-0)
| description: | updated |
| John Chittum (jchittum) wrote | #1 |
| Callahan Kovacs (mr-cal) wrote | #2 |
| Sergio Schvezov (sergiusens) wrote | #3 |
| John Chittum (jchittum) wrote | #4 |
| Changed in cloud-images: | |
| status: | New → Confirmed |
| John Chittum (jchittum) wrote | #5 |
| Steve Langasek (vorlon) wrote | #6 |
| Launchpad Janitor (janitor) wrote | #7 |
| Changed in livecd-rootfs (Ubuntu): | |
| status: | New → Confirmed |
| Callahan Kovacs (mr-cal) wrote | #8 |
| summary: |
- buildd daily kinetic and lunar image missing systemd-resolved + buildd daily kinetic, lunar, and mantic image missing systemd-resolved |
| John Chittum (jchittum) wrote | #9 |
| Changed in cloud-images: | |
| assignee: | nobody → Simon Poirier (simpoir) |
| status: | Confirmed → In Progress |
| Changed in livecd-rootfs (Ubuntu Lunar): | |
| status: | New → Confirmed |
| description: | updated |
starting in kinetic, systemd-resolved was separated into its own package. as i look in the livecd-rootfs code for buildd, i'm a little confused as to its package set -- i don't see an identified seed, just a copy from the existing chroot and the addition of a couple packages. which is awkward because the initial chroot is _also_ builds.
as i keep digging through, nothing is installing `systemd-resolved`, which makes me think it's missing in the initial package definitions of buildd. it's not listed as an a package to install during the config step:
https:/
this isn't affecting launchpad-buildd because of their specific networking setup. since systemd packaged resolved with it before kinetic, it feels safe to me to add in the split out package to the list in live-build/
I'm checking with cjwatson on that assertion though, as we don't want to introduce issues for launchpad.