[14:45] <fritchie> 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] <smoser> fritchie, can you get /var/log/cloud-init.log ?
[15:06] <smoser> you will probably have to make a modification to get goot logs there.
[15:07] <smoser> good logs
[15:11] <fritchie> 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] <fritchie> smoser:
[15:17] <fritchie> https://thepasteb.in/p/58hgNG6ZJoNuv
[15:32] <smoser> fritchie, in /etc/cloud/cloud.cfg.d/ you probably have a file named 05_logging.cfg
[15:33] <smoser> if it has a line like:
[15:33] <smoser> - [ *log_base, *log_syslog ]
[15:33] <smoser> then either remove that or comment ('#') it out
[15:33] <smoser> then you should get more logs there.
[15:33] <smoser> there should be more log there...
[16:00] <smoser> blackboxsw,
[16:01] <smoser> http://paste.ubuntu.com/25191361/
[16:10] <blackboxsw> hah oops
[16:10] <blackboxsw> didn't mean to rage quite
[16:10] <blackboxsw> didn't mean to rage quit
[16:10] <blackboxsw> smoser: you said you'll get me a couple of something
[16:10] <smoser> fritchie, 0.7.9... did that work for you?
[16:10] <blackboxsw> then I fatfingered the close hangout window
[16:10] <smoser> now orries.
[16:10] <smoser> worries
[16:15] <blackboxsw> smoser: dhclient works on centos AWS without -q.  one win
[16:20] <fritchie> smoser, i'll try in a bit, thx
[16:31] <fritchie> smoser: more logs now
[16:31] <fritchie> https://thepasteb.in/p/zmh8V2wO3oquZ
[16:32] <blackboxsw> and works w/out dhclient -I on  ubuntu. ok. the world is simpler than I thought.
[16:34] <smoser> fritchie, so it looks like cloud-init-final isn't running. this is centos 6 ? or centos 7?
[16:36] <smoser> either systemctl status cloud-init-final
[16:36] <smoser> or
[16:36] <fritchie> 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] <smoser> k
[19:28] <powersj> blackboxsw: what's the fastest way to install build-deps for cloud-init now? didn't you have a script?
[19:29] <blackboxsw> make ci-deps-ubuntu or make ci-deps-centos
[19:29] <blackboxsw> powersj: ^
[19:31] <powersj> blackboxsw: thanks!
[19:35] <powersj> blackboxsw: http://paste.ubuntu.com/25192636/
[19:37] <blackboxsw> oops, I must've botched something on a previous run. will propose a trivial patch in a  couple mins powersj
[19:40] <powersj> blackboxsw: yep http://paste.ubuntu.com/25192658/
[19:40] <powersj> I think just the extra -
[19:41] <blackboxsw> patch accepted. sorry had to wrap up another branch 1st.
[19:49] <blackboxsw> powersj: pushed to master
[19:49] <blackboxsw> 80bf98b..664a220
[19:51] <powersj> blackboxsw: thx
[20:12] <smoser> blackboxsw, your'e good to merge your other branch
[20:12] <smoser> https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/327827
[20:13] <blackboxsw> sweet smoser  thx
[20:13] <blackboxsw> errr...  sweet! smoser, thanks.
[20:13] <blackboxsw> punctuation makes all the difference
[20:36] <powersj> bah so bddeb expects you to be in the root directory
[20:36] <powersj> which has broken the tree-run of the integration tests
[20:56] <blackboxsw> 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] <blackboxsw> 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] <blackboxsw> 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] <powersj> blackboxsw: I'm making integration tests figure it out, but running into missing dependencies now :\
[20:57] <powersj>                 make[2]: nosetests3: Command not found
[20:57] <powersj> which is not in requirements.txt or test-requirements.txt
[20:57] <blackboxsw> lame
[20:58] <powersj> I'll propose my workarounds tonight and you can look on monday