=== natorious is now known as zz_natorious === zz_natorious is now known as natorious [00:32] hey can anyone help me figure out why my cloud-config isn't working? [00:33] /var/lib/cloud/instances/i-dca1cb75/user-data.txt has base64-encoded text [00:33] that decodes to a #cloud-config file === natorious is now known as zz_natorious === zz_natorious is now known as natorious === mfisch is now known as Guest68660 === natorious is now known as zz_natorious [13:19] anotheral, it shouldnt be base64 encoded there. === zz_natorious is now known as natorious === Guest68660 is now known as mfisch === mfisch is now known as Guest81226 [14:53] smoser: I'd like to submit a talk to LinuxCon Europe/CloudOpen Europe (they're running at the same time in the same place); I was thinking that cloud-init 2.0 would be a good topic. [14:53] smoser: Would you be able to help me craft a talk proposal? === mfisch is now known as Guest25676 [14:57] sure === Guest25676 is now known as mfisch [16:36] smoser: CFP ends tomorrow; I'll try and come up with something tomorrow morning, and we can maybe discuss it on/just after the 2.0 call? [16:36] smoser: (I've fixed the tests on that CloudStack MP) [16:36] ok [16:41] Odd_Bloke, pulled [16:42] smoser: Thank you, sir. [16:43] I'll look at backporting it tomorrow also. [16:44] smoser: Are you able to add all the releases back to precise as targets on https://bugs.launchpad.net/cloud-init/+bug/1464253 ? [16:45] oh. you marked that security. [16:46] why is that different then the non-security one ? [16:46] (i had thought it was the cpc bug or something) [16:46] smoser: The other bug is actually about doing it every boot (which I don't think we want to be the default). [16:46] oh. i see. [16:46] smoser: Someone just noted the security issue in the comments of that bug. [16:47] well, why idd you mark 'fixes' [16:47] which made me mark fixes ;) [16:47] >.< [16:48] Apologies. [16:48] Wasn't it easier when I use git-bzr-ng and couldn't use --fixes at all. ;) [16:56] smoser: Do you mind if I assign doing the devel release to you? [17:00] context ? [17:00] smoser: The release of that security fix in to wily. === natorious is now known as zz_natorious [18:05] I have a redhat atomic host I'm trying to run subscription-manager register on via runcmd but it doesn't appear to run and there's no output in /var/log/cloud-init.log (debug: true is set) [18:06] other commands in runcmd work though. Is there a way I can tell cloud-init to parse a user-data file again so I can see it run and try to debug it? [18:08] running the command manually after the system is booted works without issue [18:33] alexpilotti : Hi there, smoser told me yesterday you might have a better idea for my issue, any chance you being around ? [18:46] jgarr, runcmd stuff is run in 2 parts. [18:50] jgarr, so.. the first part, writes /var/lib/cloud/instance/scripts/runcmd from what it finds in user-data [18:50] so you can check to see that you have that file [18:52] that part is the 'runcmd' config job. it can be regenerated by: [18:52] cloud-init single --name=runcmd --frequency=always [18:53] the second part is in scripts_user [18:53] and it actually executes (via run-parts style) all programs in /var/lib/cloud/instance/scripts/runcmd [18:53] that can be executed: [18:54] cloud-init single --name=scripts_user --frequency=always === zz_natorious is now known as natorious === natorious is now known as zz_natorious === zz_natorious is now known as natorious [20:59] smoser: thanks a ton for that. I'll look at my host and see what I have [21:23] smoser: i removed the base64 encoding, but it still doesn't set the hostname [22:20] smoser: sure enough. the runcmd file doesn't exist. runing cloud-init single doesn't generate it either. Now to figure out why [22:20] may be helpful to say I'm also doing this on hardware with --append"ds=nocloud\;seedfrom=/var/cloud-init/" and then putting meta-data and user-data in /var/cloud-init/ === natorious is now known as zz_natorious