From: Loic Dachary <loic@dachary.org>
To: Mehdi Abaakouk <sileht@sileht.net>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: cloud-init resolv.conf updates
Date: Thu, 11 Jun 2015 23:37:39 +0200 [thread overview]
Message-ID: <5579FFA3.2060903@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]
Hi Mehdi,
I tried to
manage_resolv_conf: true
resolv_conf:
nameservers: ['8.8.4.4', '8.8.8.8']
but did not get any result and according to /var/log/cloud-init.log it does not seem to be taken into account.
It looks like this is still an open issue according to
https://answers.launchpad.net/ubuntu/+source/cloud-init/+question/234041
https://bugs.launchpad.net/cloud-init/+bug/1394061
even when you get past the misleading example that spells manage-resolv-conf instead of manag_resolv_conf at
http://cloudinit.readthedocs.org/en/stable/topics/examples.html#configure-an-instances-resolv-conf
It looks like there would be a need to add
cloud_config_modules:
- resolv_conf
according to http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/doc/examples/cloud-config.txt#L300 but I don't know which modules I need and which are optional and if the list is going to be merged with the default or override.
so I ended up doing:
#cloud-config
bootcmd:
- echo "nameserver 10.0.3.31" | sudo tee -a /etc/resolvconf/resolv.conf.d/head
- sudo resolvconf -u
Which works for Ubuntu 14.04 but isn't going to work for every operating system ;-)
I'm sure you faced something similar in the past and I'd very much appreciate a pointer in the right direction.
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2015-06-11 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 21:37 Loic Dachary [this message]
2015-06-12 5:01 ` cloud-init resolv.conf updates Alexandre DERUMIER
2015-06-12 5:57 ` Alexandre DERUMIER
2015-06-12 7:17 ` Loic Dachary
2015-06-12 8:02 ` Alexandre DERUMIER
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5579FFA3.2060903@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sileht@sileht.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.