Comment 9 for bug 1659639

This is weird... It feels like we're trying to use a space, but end up using the wrong one for some reason.

$ juju spaces
Space Subnets
db
dbb
dbc 172.30.100.0/24
       172.30.101.0/24
       172.30.102.0/24
pub 172.30.2.0/24
pub-2 172.30.200.0/24
       172.30.201.0/24
       172.30.202.0/24

(dbc is the 100 range, pub-2 is the 200 range)

$ juju deploy --bind pub-2
$ juju show-machine 5
machines:
  "5":
...
    network-interfaces:
      eth0:
        ip-addresses:
        - 172.30.1.209
        mac-address: 02:59:e4:10:5f:11
        is-up: true
$ juju deploy --bind dbc
$ juju show-machine 5
machines:
  "6":
...
    network-interfaces:
      eth0:
        ip-addresses:
        - 172.30.200.111
        mac-address: 06:bd:24:3c:ac:67
        space: pub-2

So the instance that was supposed to be in "dbc" ended up in pub-2 and the machine that was supposed to be in 'pub-2' ended up in "".