Comment 10 for bug 1560201

Ah, every watcher is automatically started off with a single "change", basically a snapshot of the model at that moment. Subsequent Next() calls for the same watcher will block until the next change.

So, it may be that jujuclient.py is making some assumptions (e.g. in get_stat()) that no longer hold true in the multi-model-controller world of Juju 2.0. Did you run into the problem originally while using jujuclient.py or via some other code?