So it starts with:
2015-06-11 18:57:06 ERROR juju.apiserver images.go:47 GET(/environment/fc4d4b2e-d601-4303-8ff9-c309ddc26fdc/images/lxc/trusty/amd64/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz?%3Aarch=amd64&%3Aenvuuid=fc4d4b2e-d601-4303-8ff9-c309ddc26fdc&%3Afilename=ubuntu-14.04-server-cloudimg-amd64-root.tar.gz&%3Akind=lxc&%3Aseries=trusty&) failed: while streaming image: write tcp 127.0.0.1:50781: broken pipe
but that is followed by:
2015-06-11 19:20:18 ERROR juju.apiserver debuglog.go:110 debug-log handler error: write tcp 10.172.68.236:58562: broken pipe
That looks a whole lot like networking broke. Because it was trying to write a message to 10.172.68.236 at a random port, which looks a lot like a client side connection. Though it is 30 minutes later, and the next errors about lease manager are from 11h30m later.
Followed more failures and then:
2015-06-14 18:12:28 ERROR juju.worker.charmrevisionworker revisionupdater.go:86 cannot process charms: finding charm revision info: cannot get metadata from the charm store: cannot unmarshal error response "<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n": invalid character '<' looking for beginning of value.
I'll do a quick spin up to see if I can reproduce, but it certainly looks strange.
So it starts with: t/fc4d4b2e- d601-4303- 8ff9-c309ddc26f dc/images/ lxc/trusty/ amd64/ubuntu- 14.04-server- cloudimg- amd64-root. tar.gz? %3Aarch= amd64&% 3Aenvuuid= fc4d4b2e- d601-4303- 8ff9-c309ddc26f dc&%3Afilename= ubuntu- 14.04-server- cloudimg- amd64-root. tar.gz& %3Akind= lxc&%3Aseries= trusty& ) failed: while streaming image: write tcp 127.0.0.1:50781: broken pipe
2015-06-11 18:57:06 ERROR juju.apiserver images.go:47 GET(/environmen
but that is followed by: 68.236: 58562: broken pipe
2015-06-11 19:20:18 ERROR juju.apiserver debuglog.go:110 debug-log handler error: write tcp 10.172.
That looks a whole lot like networking broke. Because it was trying to write a message to 10.172.68.236 at a random port, which looks a lot like a client side connection. Though it is 30 minutes later, and the next errors about lease manager are from 11h30m later.
Followed more failures and then: charmrevisionwo rker revisionupdater .go:86 cannot process charms: finding charm revision info: cannot get metadata from the charm store: cannot unmarshal error response "<html> <body>< h1>503 Service Unavailable< /h1>\nNo server is available to handle this request. \n</body> </html> \n": invalid character '<' looking for beginning of value.
2015-06-14 18:12:28 ERROR juju.worker.
I'll do a quick spin up to see if I can reproduce, but it certainly looks strange.