[10:27] <bartuss7> Hello. I'm trying to inject dns to /etc/resolv.conf using userdata, but doesnt work. I'm using heat to inject resolv config. Here is my config: https://pastebin.com/dhW2SgZy
[11:25] <chele> hi there, how can i disable dhcp and provide static network config?
[11:26] <chele> i saw this bugs from last summer but not resolution so far https://bugs.launchpad.net/cloud-init/+bug/1633656
[14:05] <smoser> bartuss7: any time someone pastes a pastebin.com, my eyes make me tell them 2 things
[14:06] <smoser> a.) pastebinit (pacakge, installed in ubuntu by default) . uses http://paste.ubuntu.com .
[14:06] <smoser> b.) my favorite pastebin (although i fear it wont last long) https://hastebin.com/
[14:07] <smoser> now... done witih public service announcement, i'll look at what you have.
[14:11] <smoser> bartuss7: a few things i suspect.
[14:12] <smoser> a.) the 'resolv_conf' module isnt enabled by default. you'd have to add it to /etc/cloud/cloud.cfg (init_modules).
[14:12] <smoser> b.) i dont know if heat will magically add the '#cloud-config' header or not
[14:13] <smoser> but you have to have that or cloud-init will not pay attention to the content (it does  not assume that all data is always for it).
[14:13] <smoser> c. in openstack... y ou can proably manaage your nameservers differentlky through network settings and it should all get through.
[14:14] <smoser> chele: need some more data.
[14:14] <smoser> are you using uvtool ?
[14:15] <chele> smoser right
[14:15] <chele> i think my college solved with user_data.cfg
[14:15] <smoser> chele: so i assume that its just a missing feature.
[14:16] <smoser> let me see if there is a way in uvtool to manage it via network-config
[14:16] <chele> but according to the bug report it still tried dhcp and ...
[14:16] <chele> right
[14:44] <smoser> chele: http://paste.ubuntu.com/26464399/
[14:44] <smoser> i'll update that bug with this
[14:46] <chele> smoser right, so this doesn't fire dhcp req?
[14:46] <smoser> correct. it gives the static configuration describec by that ENI file
[14:47] <smoser> and should work 14.04 -> 18.04
[14:47] <chele> right. ok so i guess bug might be fixed but nobody update the bug report...anyway thanks.
[14:50] <smoser> chele: well this is not an ideal situation really.
[14:51] <smoser> it will work. just not ideal. see the caveats i wrote there.
[14:52] <smoser> hi might be wrong about 14.04
[14:53] <chele> right.
[19:02] <smoser> rharper blackboxsw powersj fyi, yesterday i turned on auto-expire of Incomplete bugs.
[19:02] <smoser> which is why you might see some mail
[19:02] <powersj> "some"
[19:03] <powersj> ;) and yes got 40+ this morning
[19:04] <smoser> rharper: https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/336630
[19:04] <smoser> you want to finish-approve that ?
[19:19] <rharper> smoser: looking
[19:23] <rharper> smoser: approved; but generally I didn't understand why we wouldn't have the list of labels we recognize in one place (or at least one in python and one for ds-identify )
[19:24] <smoser> rharper: it *is* in one place.
[19:24] <smoser> only in ds-identify.
[19:26] <rharper> ok
[21:22] <smoser> powersj: https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/336722
[21:23] <smoser> that i think would magically start working when lxd 3 lands in whaever snap channel we're using.
[21:25] <powersj> smoser: thanks! where did you find the info about lxd 3.0?
[21:25] <powersj> I can give it a shot in a bit too
[21:26] <powersj> oh sorry now I see your comment in the bug
[21:27] <smoser> yeah, ikind of would like to have the currrently-working path in place too
[21:27] <smoser> i dropped the _setup_console_log bit before i knew that '--show-console-log' didn't actually work  :)
[23:21] <blackboxsw> thanks for the reviews smoser rharper thanks for the good review on my doc branch, I think I addressed all comments and reworked a lot of the content and cross reference links.