[00:09] <sedition> anyone have an idea on why an init script would be completely ignoring the packages and runcmd blocks? it sets up my users just fine and then fails to install packages/run commands silently. nothing in the cloud-init-output.log indicates that it even tried
[00:20] <rharper> sedition: /var/log/cloud-init.log should have some info on what got run (it won't have your script output);  but maybe a reason why it couldn't run it;
[13:27] <smoser> sedition, did you find something out on your  ppa thing ?
[13:28] <smoser> the only thing i can come up with is that you did not have networkign at that poign.
[13:29] <smoser> and then as rharper stated, /var/log/cloud-init.log and var/log/cloud-init-output.log probaly have more info
[13:29] <smoser> gholms, it sounds like a unit test bug
[13:40] <davydotcom> morning, trying to use cloud-init on Debian 8.3 image however there a known bug fixed in cloud-init 0.7.7 but apt-get only pulls down 0.7.6, how can i get 0.7.7 is on this version of debian
[14:07] <smoser> davydotcom, https://packages.qa.debian.org/c/cloud-init.html
[14:07] <smoser> stable has 0.7.9
[14:07] <smoser> you might be able to just use that package, or build your own for older debian. i'm not aware of any othe rbackported option
[14:08] <davydotcom> smoser: thanks ill try that out
[14:36] <powersj> smoser: https://bugs.launchpad.net/cloud-init/+bug/1721243 might be worth looking at, he came back with a patch
[14:40] <smoser> powersj, responded
[15:03] <powersj> smoser: any comments on the patch? ;)
[15:05] <smoser> powersj, needs tests
[15:05] <smoser> but  yeah, i do have comments on it.
[15:37] <smoser> gholms, tox-venv py3 python3 -m nose tests/unittests/test_handler/test_handler_ntp.py
[15:37] <smoser> bah
[15:37] <smoser> gholms, https://bugs.launchpad.net/cloud-init/+bug/1721573
[15:37] <smoser> and rharper ^ just fyi.
[15:39] <rharper> k
[15:41] <rharper> smoser: huh, schema unit tests
[15:56] <gholms> smoser: Oh, I already filed a bug for that yesterday
[15:56] <gholms> https://bugs.launchpad.net/cloud-init/+bug/1721411
[16:02] <blackboxsw> gholms: thanks for the bug, just marked it duplicate to track under  1721573
[16:02] <gholms> Thanks
[16:02] <smoser> thanks gholms sorry for the noise
[16:02] <gholms> No worries.  Thanks for confirming.
[16:28] <sedition> smoser: i solved the ppa issue, now moving on to another script for a different server that's silently eating the runcmd and package block. hoping this morning i can attack it with fresh eyes. thank you for asking!
[16:28] <sedition> great little community
[16:48] <powersj> smoser: We just got a pull request on github
[16:48] <powersj> https://github.com/cloud-init/cloud-init/pull/9
[16:52] <dpb1> heh
[16:52] <dpb1> nice
[16:53] <dpb1> what was our policy there?  close and ask to submit to lp?
[16:53] <dpb1> and sign the cla
[16:53] <dpb1> :)
[16:53] <dpb1> larsks might know him actually
[16:58] <_ix> Good morning friends. Can someone let me in on the secret to versioning from 0.7.9 -> 17.1. How does this match up to EL Repos?
[16:58] <_ix> Running into this specific issue: https://bugs.launchpad.net/cloud-init/+bug/1699282
[16:59] <blackboxsw> hi _ix. EL repos should eventually update to 17.1. It's a recent release versioning decision that we just came too a few weeks ago with cloud-vendors & distro vendors.  More details here FYI https://lists.launchpad.net/cloud-init/msg00106.html
[17:00] <blackboxsw> checking the bug details now
[17:02] <_ix> OK. Thanks very much! I'll check back in just a few minutes.
[17:02] <blackboxsw> _ix have you been able to check our latest cloud-init builds as built in our copr repo? https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/
[17:03] <blackboxsw> repos there have tip  (which will have version 17.1+)
[17:03] <blackboxsw> in which I think we have a fix for puppet config
[18:13] <sather> Question, where do I start debugging when I get 'Failed to start Initial cloud-init job (metadata service crawler)?
[18:14] <sather> nothing 'pops' out when grepping the source code
[18:14] <sather> I ran `cloud-init --debug init`, also nothing popping out as an 'ERROR'
[18:15] <sedition> my script problem was 'sedition is an idiot'
[18:16] <sedition> apt will just silently zombie forever without internet access.
[18:16]  * sedition facedesk
[18:16] <sather> I'm running version: 0.7.5 on centos
[18:28] <_ix> blackboxsw: I'll take a look at that. Thanks!
[19:09] <rharper> smoser: https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/331892
[20:00] <blackboxsw> couple comments rharper
[20:00] <blackboxsw> https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/331892
[20:01] <rharper> blackboxsw: well this is the merge, that's already committed upstream; this is into release
[20:01] <rharper> you're right though
[20:03] <blackboxsw> ahh right, right
[20:05] <smoser> blackboxsw, so we need to fix ?
[20:05] <smoser> upstremam ? did you fidn a b ug there ?
[20:06] <blackboxsw> smoser: I think I did find a corner case, "if 0" will never get into that non-bool check to convert it to boolean
[20:06] <rharper> it's best to fix, the network config documents use of strings 'off' and 'on' ; not 0 or 1;  but nothing prevents us from getting such a config
[20:06] <blackboxsw> bridge_stp = iface.get('bridge_stp')
[20:06] <blackboxsw> 57	+        if bridge_stp and type(bridge_stp) != bool:
[20:06] <rharper> blackboxsw: yeah,  I should check if value is not None and type is not bool;
[20:06] <blackboxsw> yeah one liner
[20:07] <smoser> ok. then submit that for merge and then re-submit for package ?
[20:09] <blackboxsw> sure putting it up
[20:18] <smoser> blackboxsw, ok. i'm waiting on an MP with a fix for that bug you found.
[20:19] <smoser> then re-MP from raharper.
[20:20] <blackboxsw> smoser: pushed. writing a proper descriptiojn now
[20:21] <blackboxsw> https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/network-stp-handle-0
[20:23] <blackboxsw> https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/331898
[20:25] <smoser> ship it.
[20:26] <smoser> $ tox && git push upstream HEAD
[20:27] <smoser> (that is running here)
[20:27] <blackboxsw> merged
[20:27] <blackboxsw> bah
[20:27] <smoser> you pushed ?
[20:27] <smoser> thats fine
[20:27] <blackboxsw> yeah pushed
[20:27]  * smoser ctrl-c
[20:27] <blackboxsw> heh thx
[20:27] <smoser> ok. now raharper for ubuntu points
[20:27] <smoser> rharper,
[20:38] <rharper> smoser: ok, I'll re MP
[20:39] <smoser> good
[21:20] <rharper> blackboxsw: thanks for spotting that
[21:21] <blackboxsw> better late than never
[21:21] <blackboxsw> thanks for going through the upload gauntlet 50 times
[21:22] <rharper> smosers handy gist is super helpful
[21:22] <blackboxsw> so for our SRU change log to xenial.... does our card need to actually capture all bugs from 0.7.9~233 until tip?
[21:22] <smoser> blackboxsw, it will.
[21:22] <smoser> here.
[21:23] <blackboxsw> thanks, I was going to post-process the changelog into the trello checklist
[21:23] <smoser> http://paste.ubuntu.com/25682062/
[21:24] <blackboxsw> :( why do people do so much work? :)
[21:24] <smoser> for your reference, what i did:
[21:24] <smoser>  git checkout ubuntu/xenial
[21:24] <smoser>  ./debian/new-upstream-snapshot
[21:24] <smoser> it shows that log in a editor, i copy paste
[21:24] <smoser> say 'n'
[21:24] <smoser> then
[21:25] <smoser> git reset --hard upstream/ubuntu/xenial
[21:25] <blackboxsw> placing an bash alias function for that in my env
[21:40] <htaccess> what is the process for newer cloud-inits getting added to a distro?
[21:41] <htaccess> ie can i expect to see 17.1 in xenial cloud images?
[21:45] <rharper> htaccess: for Ubuntu, the process is here: https://wiki.ubuntu.com/StableReleaseUpdates;  and yes you can expect 17.1 to come to xenial;
[21:46] <blackboxsw> htaccess: we are working on uploading an SRU today/tomorrow to xenial at which point we need to go through verification on the related bugs. I'd expect 1-2 weeks on when you will see 17.1 in xenial. folks can correct me if that's too optimistic
[21:47] <htaccess> thanks!
[22:18] <blackboxsw> well just wrote a dumb script for trello SRU checklists from debian changelog
[22:18] <blackboxsw> heh for next time on SRU check http://paste.ubuntu.com/25682341/
[22:18] <blackboxsw> yields http://pastebin.ubuntu.com/25682350/
[22:20] <blackboxsw> looks like 13 bugs to verify instead of 7 for xenial I think'