Bug#961833: buster-pu: package openstack-debian-images/1.36

2020-07-02 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Sat, 2020-05-30 at 01:57 +0200, Thomas Goirand wrote:
> 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.
> 

Please go ahead.

Regards,

Adam



Bug#961833: buster-pu: package openstack-debian-images/1.36

2020-06-08 Thread Thomas Goirand
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)



Bug#961833: buster-pu: package openstack-debian-images/1.36

2020-05-29 Thread Thomas Goirand
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)
>From 5a386303ba1ab60acd062c800d6bc16223483c08 Mon Sep 17 00:00:00 2001
From: Thomas Goirand 
Date: Sat, 30 May 2020 01:46:11 +0200
Subject: [PATCH]   * Add the resolvconf if installing cloud-init, needed in
 case a VM gets the DNS configuration from configdrive instead of DHCP.
 More on this can be found here:
 https://bugs.launchpad.net/cloud-init/+bug/1850310.

---
 build-openstack-debian-image | 2 +-
 debian/changelog | 8 
 2 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/build-openstack-debian-image b/build-openstack-debian-image
index 0e54937..50341e9 100755
--- a/build-openstack-debian-image
+++ b/build-openstack-debian-image
@@ -456,7 +456,7 @@ else
fi
NEEDED_PACKAGES=${NEEDED_PACKAGES},dbus,ntp,unscd
if [ "${CLOUD_INIT}" = "yes" ] ; then
-   NEEDED_PACKAGES=${NEEDED_PACKAGES},cloud-init,cloud-utils
+   
NEEDED_PACKAGES=${NEEDED_PACKAGES},cloud-init,cloud-utils,resolvconf
fi
 fi
 
diff --git a/debian/changelog b/debian/changelog
index a78dd2e..190f1aa 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+openstack-debian-images (1.36+deb10u1) unstable; urgency=medium
+
+  * Add the resolvconf if installing cloud-init, needed in case a VM gets the
+DNS configuration from configdrive instead of DHCP. More on this can be
+found here: https://bugs.launchpad.net/cloud-init/+bug/1850310.
+
+ -- Thomas Goirand   Sat, 30 May 2020 01:44:38 +0200
+
 openstack-debian-images (1.36) unstable; urgency=medium
 
   * Fix-up bondvlan with OVS bridge option.
-- 
2.20.1