juju deploy is FIXED

[David Cheney]

Yay, juju deploy is fixed as of rev 683.

lucky(~/src/launchpad.net/juju-core) % juju status
machines:
0:
agent-version: 0.0.1
dns-name: ec2-184-73-11-178.compute-1.amazonaws.com
instance-id: i-dcf8fea1
1:
agent-version: 0.0.1
dns-name: ec2-107-22-65-252.compute-1.amazonaws.com
instance-id: i-c48086b9
2:
agent-version: 0.0.1
dns-name: ec2-23-20-253-79.compute-1.amazonaws.com
instance-id: i-34818749
3:
agent-version: 0.0.1
dns-name: ec2-54-242-66-243.compute-1.amazonaws.com
instance-id: i-f8818785
services:
mysql:
charm: mysql
exposed: false
units:
mysql/0:
agent-version: 0.0.1
machine: 1
public-address: ec2-107-22-65-252.compute-1.amazonaws.com
status: started
mysql/1:
agent-version: 0.0.1
machine: 2
public-address: ec2-23-20-253-79.compute-1.amazonaws.com
status: started
mysql/2:
agent-version: 0.0.1
machine: 3
public-address: ec2-54-242-66-243.compute-1.amazonaws.com
status: started


If you were the person who resolved this issue, please close https://bugs.launchpad.net/juju-core/+bug/1065342

Cheers

Dave