Comment 14 for bug 1302205

I've been trying to debug this on my own, but I'm enough of a novice that I'm not really sure where to start. Here's a couple things I've noticed..

I do see that that machine-1's jujud makes a connection to the bootstrap node that remains open for a while, but that socket later closes and never appears to reconnect. This seems to be around the time the agent-state switches to down.

I see this error on the bootstrap node (whether or not I specify the port in my environments.yaml):
/var/log/juju/machine-0.log:2014-04-08 17:08:25 ERROR juju.worker environ.go:56 loaded invalid environment configuration: storage-port: expected int, got float64(8040)

I tried to reproduce this using EC2-provisioned VMs, but the problem was not reproducible there.