Comment 8 for bug 1659639

You can work around this by passing a constraint for the machine:
series: xenial
services:
  ul-b:
    charm: "cs:~jameinel/ubuntu-lite-4"
    num_units: 2
    to:
      - "0"
      - "lxd:0"
    bindings:
      "": dbc
machines:
  "0":
    constraints: "arch=amd64 spaces=dbc"

This correctly provisions into a correct subnet.

I'm seeing weird behavior where the machine doesn't end up with a proper configuration for cloud-init. It comes up but never tries to install Juju.

Also, after having done "juju deploy ubuntu-lite --bind space" if I then do "juju add-unit" the added unit is *not* coming up in the right subnets. Hopefully the 'deploy-from-a-bundle' is the same bug as the "add-unit" bug.