arcoceppi
<thumper> now to look at maas
<bigjools> o/
<bigjools> I just got pinged about this
<thumper> hazmat: what versions were you playing with?
<bigjools> narrowed it down any yet?
<thumper> bigjools: not started looking yet
<hazmat> thumper, 1.16.0 for maas
<bigjools> thumper: I guess I should fire up my maas server? :)
<thumper> bigjools: gimmie time to shower (haven't since back from the gym yet), and we can have an initial call prior to working out debugging plan
<thumper> bigjools: ack
<sinzui> hazmat, yes, my testing tools are in place in aws and hp and canonistack. I place them in the testing/ subdir and point the tools url to them: http://juju-dist.s3.amazonaws.com/
<bigjools> thumper: roger mcdodger
<sinzui> hazmat, and I will officially make the tarball in about 10 minutes
<hazmat> smoser, it requires explicit lxc-clone -s  but yeah.. it works without specing btrfs directly
<hazmat> du -hs /var/lib/lxc/container-name -> 7mb
<sinzui> hazmat, and you can see all the scripts I am using at https://code.launchpad.net/~juju-qa/juju-core/ci-cd-scripts2
<sinzui> you can make your own deb without any juju parts installed
<wallyworld_> bigjools: how long does an juju azure bootstrap instance normally take to spin up?
<smoser> wallyworld_, ~ 5 minutes i think
<bigjools> wallyworld_: from memory not at all quick, I think it was like 5-10 m
<wallyworld_> ok, ta. just bootstrapped an and waiting for juju status
<wallyworld_> s/just/have been
<marcoceppi> thumper: can you summarize what should be logged?
<thumper> marcoceppi: the symptom was that the machines were pending, and lxc-ls --fancy showed the machines started but with no ipv4 address
<thumper> marcoceppi: ls -lh /var/cache/lxc/cloud-precise showed ubuntu-12.04-server-cloudimg-amd64-root.tar.gz to be over 4 months old
<thumper> marcoceppi: delete that file, destroy the environment and try again
<thumper> a new lxc cloud image will be downloaded and all should be good
<thumper> bigjools: hangout?
<thumper> marcoceppi: does that all make sense?
<sinzui> th