Comment 10 for bug 1785314

My use case was slightly interesting (I guess); I wanted to assign several machines (not all) as machines in specific spaces (internal network). In addition, all machines are attached to a publicly available network (undefined space). When I didn't specify bindings, I ran into deployment issues with Juju unable to decide on a space for the undefined machines. Adding in specific bindings (`"": undefined') resolved those issues but caused Juju to request these machines incorrectly.

I have since actually named the space which resolves the issue but I basically wanted to leave the default network undefined as everybody is already connected to it.