[18:12] <rhys> i’ve spent a day trying to get this to work, but can anyone tell me why the resolv-conf module does not work on centos 7 in AWS ?
[18:14] <rhys> i’ve notice that systemd is configured to execute init, config, and final all separately. i use the init chunk to install the newest version of cloud-init, and to add the “resolv-conf” module to cloud_config_modules. i then pass it user-data that includes manage-resolv-conf: true, exactly from the examples. all other directives i pass in user-data execute successfully.
[18:15] <rhys> i turn off the auto-updating of /etc/resolv.conf in /etc/sysconfig/network-scripts/ifcfg-eth0, so that dhclient doesn’t override it. but no matter what i do resolv.conf remains untouches.
[18:16] <rhys> oh. is this not the same cloud-init thats version cloud-init-0.7.6-2.el7 ? openstack and canonical have different cloud-inits? :(
[18:33] <smatzek> rhys:  I believe the samples are wrong here.  It needs to be manage_resolv_conf note the underscore character.
[18:34] <rhys> smatzek: also the module is named ‘resolv-conf’ with a dash yes?
[18:35] <smatzek> for module names in cloud.cfg they can be either dash or underscore, they get normalized in the code, but for directives that the individual modules look for in userdata, they need to match what the code is looking for.
[18:37] <smatzek> in this case the code is looking for 'manage_resolv_conf'.   http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/config/cc_resolv_conf.py#L97
[18:38] <rhys> smatzek: welp there was a day of my life gone
[18:38] <rhys> thank you so much
[18:41] <smatzek> Odd_Bloke:  are you there?
[18:55] <smatzek> rhys:  I've opened this bug to try and address the change in the documentation:  https://bugs.launchpad.net/cloud-init/+bug/1531582
[18:55] <rhys> thanks. i really appreciate it. i should have noticed the disparity
[18:55] <rhys> because i was using manage_etc_hosts too
[18:55] <smatzek> the resolv.conf one and the lock_passwd one have sucked many hours of my time and others time in the past.
[18:56] <rhys> smatzek, the interesting thing is that while its now working, its writing the resolv.conf template raw
[18:56] <rhys> its not evaluating the template
[18:57] <rhys> actually thats now true of all modules.
[18:57] <rhys> like etc/hosts now has 127.0.0.1 {{fqdn}} {{hostname}}
[18:58] <rhys> in the logs. Jan  6 18:54:48 localhost cloud-init: 2016-01-06 18:54:48,271 - templater.py[WARNING]: Jinja not available as the selected renderer for desired template, reverting to the basic renderer.
[19:01] <rhys> package build problem. found the bug
[23:14] <harlowja> smoser did u guys meetup in england yet?