Comment 5 for bug 1646310

Incidentally, changing that value to Running instead of Started just means that something else breaks when the migration starts - the status of the minimal application I have deployed changes to:

    units:
      min/0:
        workload-status:
          current: unknown
          since: 01 Dec 2016 18:05:28+13:00
        juju-status:
          current: failed
          message: resolver loop error
          since: 01 Dec 2016 18:20:50+13:00
          version: 2.1-beta2.1
        machine: "0"
        public-address: 10.218.39.138