Comment 2 for bug 1570917

FYI, I ran into this too. The solution?

  juju upgrade-juju -m default 2.0-rc1.3

In other words, upgrading juju on your controller does *not* automatically upgrade juju on your models. The question is, should it? Not necessarily. I can imagine use cases where the admin might not want to automatically upgrade all models. Regardless here are the options I see:

1. do nothing (rely on users to know to upgrade juju per-model)
2. clearly point this out in the documentation
3. add a note in the output of "juju upgrade-juju --upload-tools" reminding admins to manually upgrade each model
4. make the "juju is out-of-date" warnings also show up for models relative to the controller
5. auto-upgrade models when the controller is upgraded
6. auto-upgrade but have a flag to not auto-upgrade
7. have a flag to auto-upgrade