[15:18] hi all, how to debug datasource discovery ? `cloud-init -d init` not initializing it, can`t debug configdrive descovery [15:19] fxpester, [15:20] hihi [15:24] in 'normal' logs I can see `Command: ['mount', '-o', 'ro,sync', '-t', 'auto', '/dev/sda1', '/tmp/tmpxamurqwn']` [15:24] but can`t find a way to reproduce it [16:11] fxpester, possibly you dont have a module loaded at that point in boot that you need and gets loaded later ? [16:11] what kernel /distro is this ? [16:11] if you could post both /var/log/cloud-init.log and /var/log/cloud-init-output.log tha'td hhelp [16:12] and also a dmesg maybe [16:25] hey all [16:25] 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] hey Tugz, checking /etc/cloud/cloud.cfg should list module names that are configured for your environment. [16:28] look under cloud_init_modules, cloud_config_modules and cloud_final_modules sections for the complete list [16:28] of enabled modules [16:28] I'd expect - disk_setup listed under cloud_init_modules section [16:29] - growpart [16:29] - resizefs [16:29] - disk_setup [16:29] are on my ubuntu instance [16:34] 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] Ubuntu bug 1672833 in cloud-init "AWS NVME SSD (i3 family) ephemeral storage fails to mount via fs_setup" [Medium,Invalid] [16:34] https://bugs.launchpad.net/cloud-init/+bug/1672833/comments/4 [16:34] hackery to fixup in that comment if that's the case for your cent7 image [17:28] hey blackboxsw where is this section? [17:30] oh its on the .cfg found it [17:30] thanks [17:30] Tugz: older releases of cloud-init may not have the specific key name, but yeah /etc/cloud/cloud.cfg [17:30] how do i know if this version of cloud init supports the modules? [17:35] 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] the module is then enabled only if it is listed in /etc/cloud/cloud.cfg [17:36] so different platforms/images can "disable" a module by not listing the named module in /etc/cloud/cloud.cfg [17:36] even if it is installed in /usr/lib/python2.7/site-packages/cloudinit/config/cc_*py [17:37] 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] blackboxsw, thanks fo rthe valuable info. much appreciated [17:49] no worries Tugz, happy hacking [21:44] 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] Ubuntu bug 1701097 in cloud-init (Ubuntu Zesty) "eni rendering of ipv6 gateways fails" [Medium,Fix committed] [21:44] It see it twice in our SRU list [21:55] blackboxsw: well, we get one for free then [21:56] yeah already at 70%. man long day [21:56] 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] it'd assist with half of these [21:57] too many other fish to fry at the moment [22:01] blackboxsw: heh [22:01] * rharper has PYTHONPATH=`pwd` ./tools/net-convert.py in history [22:01] but, yeah, would be nice to have it in subcommands [22:02] also, s/network_data.json/json in the input format parameter [22:10] smoser: I'll probably need an assist validating SRU bug #1638931 [22:10] bug 1638931 in cloud-init "enable AliYun datasource by default" [Medium,Confirmed] https://launchpad.net/bugs/1638931 [22:10] as I have no aliyun acct