[17:59] <smoser> rharper, or blackboxsw review of https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/323059 appreciated
[18:00] <blackboxsw> looking now
[18:02] <rharper> ack
[18:02] <smoser> i'm looking at the i386 fail
[18:02] <smoser> hm..
[18:02] <smoser> that is very odd
[19:58] <smoser> powersj, around ?
[19:58] <smoser> whats the environment https://jenkins.ubuntu.com/server/job/cloud-init-ci/nodes=vm-i386/308/console
[19:58] <powersj> smoser: I am
[19:58] <powersj> i386 is a IS owned VM
[19:58] <smoser> i can't reproduce that in a i386 container or in a i386 vm
[20:00] <powersj> wow that is very interesting to see it fail only there hmm
[20:11] <powersj> smoser: what type of lxd did you use? that is a trusty i386 VM. I'll try myself in a sec.
[20:12] <smoser> powersj, i ran xenial i386 host is artsy
[20:12] <smoser> and i tried server stack xenial i386 kvm
[20:28] <powersj> smoser: `lxc launch ubuntu-daily:trusty/i386 t32` reproduced it after installing 'git python-tox'
[20:29] <powersj> well, it failed, but different error, doh :\ nose.proxy.KeyError: 'datasource_list'
[20:39] <smoser> powersj, what is 'git python-tox' ?
[20:39] <smoser> oh. those two packages
[20:39] <powersj> sorry.... apt-get install git python-tox
[20:39] <powersj> yeah
[20:39] <smoser> i thought you were using 'git' to install 'python tox'
[20:39] <smoser> duh
[20:40] <smoser> man. this little trip down trusty memory lane shows me how much improvment there was in apt
[21:03] <blackboxsw> smoser: more comments on your branch. it took me a while to formulate some thoughts on it.
[21:03] <smoser> k
[21:03] <smoser> i am oging ot have to r un
[21:04] <smoser> there is a shell bug/difference in trusty and xenial that my code is exposing
[21:04] <smoser> horay