[15:18] <fxpester> hi all, how to debug datasource discovery ? `cloud-init -d init` not initializing it, can`t debug configdrive descovery
[15:19] <smoser> fxpester,
[15:20] <fxpester> hihi
[15:24] <fxpester> in 'normal' logs I can see  `Command: ['mount', '-o', 'ro,sync', '-t', 'auto', '/dev/sda1', '/tmp/tmpxamurqwn']`
[15:24] <fxpester> but can`t find a way to reproduce it
[16:11] <smoser> fxpester, possibly you dont have a module loaded at that point in boot that you need and gets loaded later ?
[16:11] <smoser> what kernel /distro is this ?
[16:11] <smoser> if you could post both /var/log/cloud-init.log and /var/log/cloud-init-output.log tha'td hhelp
[16:12] <smoser> and also a dmesg maybe
[16:25] <Tugz> hey all
[16:25] <Tugz> question: how do i know which modules cloud-init 0.7.5 supports? This is on cnetos 7 and im trying to use disk_setup and fs_setup without success :(
[16:27] <blackboxsw> hey Tugz, checking  /etc/cloud/cloud.cfg should list module names that are configured for your environment.
[16:28] <blackboxsw> look under cloud_init_modules, cloud_config_modules and cloud_final_modules sections for the complete list
[16:28] <blackboxsw> of enabled modules
[16:28] <blackboxsw> I'd expect - disk_setup listed under cloud_init_modules section
[16:29] <blackboxsw>  - growpart
[16:29] <blackboxsw>  - resizefs
[16:29] <blackboxsw>  - disk_setup
[16:29] <blackboxsw>  are on my ubuntu instance
[16:34] <rharper> Tugz: this may be related, https://bugs.launchpad.net/cloud-init/+bug/1672833 , the tl;dr was that the disk_setup module wasn't included in the /etc/cloud/cloud.cfg in some older releases;
[16:34] <rharper> https://bugs.launchpad.net/cloud-init/+bug/1672833/comments/4
[16:34] <rharper> hackery to fixup in that comment if that's the case for your cent7 image
[17:28] <Tugz> hey blackboxsw where is this section?
[17:30] <Tugz> oh its on the .cfg found it
[17:30] <Tugz> thanks
[17:30] <blackboxsw> Tugz: older releases of cloud-init may not have the specific key name, but yeah /etc/cloud/cloud.cfg
[17:30] <Tugz> how do i know if this version of cloud init supports the modules?
[17:35] <blackboxsw> if the module exists on the config modules directory for your version then it is "available" on your platform.  Modules are all named cc_*py:     'rpm -ql cloud-init | grep cc_'
[17:35] <blackboxsw> the module is then enabled only if it is listed in /etc/cloud/cloud.cfg
[17:36] <blackboxsw> so different platforms/images can "disable" a module by not listing the named module in /etc/cloud/cloud.cfg
[17:36] <blackboxsw> even if it is installed in /usr/lib/python2.7/site-packages/cloudinit/config/cc_*py
[17:37] <blackboxsw> as a note, we just talked about the potential of surfacing a cmdline utility to do this introspection on your behalf to easily report availability && enabled/disabled for given features/modules
[17:49] <Tugz> blackboxsw, thanks fo rthe valuable info. much appreciated
[17:49] <blackboxsw> no worries Tugz, happy hacking
[21:44] <blackboxsw> hrm looks like we had dupes in https://trello.com/c/CAjwe8LX/273-cloud-init-sru-zesty-xenial for https://bugs.launchpad.net/cloud-init/+bug/1701097
[21:44] <blackboxsw> It see it twice in our SRU list
[21:55] <rharper> blackboxsw: well, we get one for free then
[21:56] <blackboxsw> yeah already at 70%. man long day
[21:56] <blackboxsw> verifications 'r us
[21:57]  * blackboxsw needs to get a branch up to include net-convert in "cloud-init  devel" at some point
[21:57] <blackboxsw> it'd assist with half of these
[21:57] <blackboxsw> too many other fish to fry at the moment
[22:01] <rharper> blackboxsw: heh
[22:01]  * rharper has PYTHONPATH=`pwd` ./tools/net-convert.py  in history 
[22:01] <rharper> but, yeah, would be nice to have it in subcommands
[22:02] <rharper> also, s/network_data.json/json in the input format parameter
[22:10] <blackboxsw> smoser: I'll probably need an assist validating SRU bug #1638931
[22:10] <blackboxsw> as I have no aliyun acct