Ian Wienand b403efdbb9 Revert "Stop systemd-resolve from booting on our images" ... This reverts commit da15523595. systemd-resolved was not really involed in this. What seems to be happening is that during the initial chroot creation there is no /etc/resolv.conf file, and so the systemd postinst script creates one pointing to the compatability files created by systemd-resolved. This is not what we want, but dib doesn't really provide a way for us to overwrite the file. That is covered in Ie0e97d8072e2b21a54b053fa6fb07b62960c686d We actually want systemd-resolved running -- it provides the dbus nameserver api stuff that some tools may use. If /etc/resolv.conf is a file, systemd-resolved leaves it alone and uses it for resolution as you would expect. (we do, however, want to wait for the depends-on to ensure the image has a correct /etc/resolv.conf before merging this). Depends-On: https://review.openstack.org/557842/ Change-Id: Ie3cdc323bf8fb4fcee725f9a52bf53a4a6a01bbf		2018-04-03 15:32:27 +10:00
..
elements	Revert "Stop systemd-resolve from booting on our images"	2018-04-03 15:32:27 +10:00
scripts	Good bye jenkins/scripts	2018-03-05 14:28:42 +01:00
nb03.openstack.org.yaml	Remove etcd version workaround for arm64	2018-03-29 15:46:34 +11:00
nl01.openstack.org.yaml	Add ubuntu-bionic to nodepool	2018-02-27 06:56:41 -05:00
nl02.openstack.org.yaml	Ramp limestone up to 50 instances	2018-04-02 13:27:16 -07:00
nl03.openstack.org.yaml	Bring vexxhost back online for testing	2018-03-19 15:00:32 -04:00
nl04.openstack.org.yaml	Set launch-timeout to 600 for OVH	2018-03-24 07:36:52 -04:00
nodepool.yaml	Add limestone to nodepool builder and launcher configuration	2018-03-23 09:25:02 -04:00