deploying to a container of nonexistent machine breaks the GUI

[frankban]

Copied from https://bugs.launchpad.net/juju/+bug/1640499

When you run juju deploy application --to lxd:1 when lxd:1 doesn't exist gives very strange behavior.

What I expect: Either Juju throws an error, or it creates machine 1 for me.

What I get: Unit has broken "waiting for machine" state. Unit stays in that state even after creating machine 1 manually. When committing changes in the gui, regardless of what the changes are, the gui keeps on adding machines to the changelist until you click "deploy". This caused the model to request 164 machines from our maas cluster.

There are two when you have a model in this state:

1. destroy the model from the gui
2. destroy the application using the commandline

Juju version 2.0.1

[clagom]

Is this still relevant?

[hatched]

Investigation will be needed, however this issue is pretty narrow and wouldn't exist with the new GUI.