Comment 4 for bug 1785223

Hello,

We are using common, long running, controller which was bootstrapped a long time ago so I did not have to bootstrap it.

The model was added using internally written automation tooling, if needed we can provide you with source code.

Once model was in place we used mojo to deploy the environment, here is the spec:
https://code.launchpad.net/~jacekn/canonical-mojo-specs/nagios

And once deployed I run the following commands:
$ juju offer nagios:monitor
$ juju offers

I run both of them from the same shell, one after another. At this stage there was no 2nd controller or model involved. I created an offer and simply wanted to confirm it was in place.

This does not work either:
$ juju offers -m <ctrlname>:prod-nagios

I tried:
$ juju offers -m prodstack-is:prod-nagios
ERROR model prodstack-is:prod-nagios/prod-nagios not found

In above output username is incorrect. Juju uses "prod-nagios/prod-nagios" but it should be "admin/prod-nagios" as per "juju models" output:

$ juju models
Controller: prodstack-is

Model Cloud/Region Status Machines Cores Access Last connection
admin/prod-nagios* prodstack-45/bootstack-ps45 available 1 1 admin 7 minutes ago

I also tried this:
$ juju offers -m prodstack-is:admin/prod-nagios
ERROR model "prod-nagios/prod-nagios" not found (not found)

But this makes it ignore controller name.