On 5/30/20 2:10 AM, Thomas Goirand wrote: > Package: release.debian.org > Severity: normal > Tags: buster > User: release.debian....@packages.debian.org > Usertags: pu > > Dear release team, > > tl;dr: if not using a DHCP to boot VMs, cloud-init would get the DNS > addresses from the configdrive, which only works if resolvconf is > installed. The attached patch fixes this. > > I'd like to add the "resolvconf" package to the official Debian OpenStack > image for Buster. Doing so is done by simply adding the package to the list > in openstack-debian-images/1.36. See attached debdiff. Once the package > reaches Buster, the new OpenStack image will include resolv.conf. Hopefully, > I can ask Steve to use the updated openstack-debian-images/1.36+deb10u1 > before openstack-debian-images moves from proposed-updates to Buster. > > Rational for fixing this can be found here: > https://bugs.launchpad.net/cloud-init/+bug/1850310 > > and in this debian-cloud thread (not only the first message, but also > the follow-ups): > https://lists.debian.org/debian-cloud/2020/05/msg00086.html > > Also, the launchpad bug above mention tests from multiple people, which > is why it feels like a safe change. > > Since I don't think a DHCP-less cloud system is uncommon, it'd be really > nice to fix this (by adding the resolvconf package in the default > OpenStack image, which implies fixing the openstack-debian-images in > Buster). > > Your thoughts? > > Cheers, > > Thomas Goirand (zigo)
Ping? Please don't reply just and only right before the point release... Cheers, Thomas Goirand (zigo)