[14:45] has anyone else seen cloud-init scripts fail to run on stock centos cloud images while the same cloud-init scripts work fine on ubuntu cloud image? it looks like the centos build doesn't even attempt to execute anything even though all the files in /var/lib/cloud look fine [15:06] fritchie, can you get /var/log/cloud-init.log ? [15:06] you will probably have to make a modification to get goot logs there. [15:07] good logs [15:11] smoser, sure ... I updated cloud-init to 0.7.9 from 0.7.4 and the script runs fine on centos ... I am using the "nocloud" data source [15:17] smoser: [15:17] https://thepasteb.in/p/58hgNG6ZJoNuv [15:32] fritchie, in /etc/cloud/cloud.cfg.d/ you probably have a file named 05_logging.cfg [15:33] if it has a line like: [15:33] - [ *log_base, *log_syslog ] [15:33] then either remove that or comment ('#') it out [15:33] then you should get more logs there. [15:33] there should be more log there... [16:00] blackboxsw, [16:01] http://paste.ubuntu.com/25191361/ [16:10] hah oops [16:10] didn't mean to rage quite [16:10] didn't mean to rage quit [16:10] smoser: you said you'll get me a couple of something [16:10] fritchie, 0.7.9... did that work for you? [16:10] then I fatfingered the close hangout window [16:10] now orries. [16:10] worries [16:15] smoser: dhclient works on centos AWS without -q. one win [16:20] smoser, i'll try in a bit, thx [16:31] smoser: more logs now [16:31] https://thepasteb.in/p/zmh8V2wO3oquZ [16:32] and works w/out dhclient -I on ubuntu. ok. the world is simpler than I thought. [16:34] fritchie, so it looks like cloud-init-final isn't running. this is centos 6 ? or centos 7? [16:36] either systemctl status cloud-init-final [16:36] or [16:36] smoser, centos 6 ... but it looks like the scripts are running now ... it was a late night of troubleshooting and maybe I made a mistake [16:36] k [19:28] blackboxsw: what's the fastest way to install build-deps for cloud-init now? didn't you have a script? [19:29] make ci-deps-ubuntu or make ci-deps-centos [19:29] powersj: ^ [19:31] blackboxsw: thanks! [19:35] blackboxsw: http://paste.ubuntu.com/25192636/ [19:37] oops, I must've botched something on a previous run. will propose a trivial patch in a couple mins powersj [19:40] blackboxsw: yep http://paste.ubuntu.com/25192658/ [19:40] I think just the extra - [19:41] patch accepted. sorry had to wrap up another branch 1st. [19:49] powersj: pushed to master [19:49] 80bf98b..664a220 [19:51] blackboxsw: thx [20:12] blackboxsw, your'e good to merge your other branch [20:12] https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/327827 [20:13] sweet smoser thx [20:13] errr... sweet! smoser, thanks. [20:13] punctuation makes all the difference [20:36] bah so bddeb expects you to be in the root directory [20:36] which has broken the tree-run of the integration tests [20:56] ok so review pass one on vmware branch is done. I'll have to get to the other tonight. family just arrived a bit early [20:56] powersj: so we need to tweak bddeb to be more flexible? or can integration tests cd to that root dir before running it [20:57] yeah those script don't really *need* to be in the root directory. they just do an initial status check to see if any setup.py exists right? [20:57] blackboxsw: I'm making integration tests figure it out, but running into missing dependencies now :\ [20:57] make[2]: nosetests3: Command not found [20:57] which is not in requirements.txt or test-requirements.txt [20:57] lame [20:58] I'll propose my workarounds tonight and you can look on monday