Cannot talk to a new model with a reused name

Bug #1576359 reported by Cheryl Jennings on 2016-04-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju
Medium
Unassigned

Bug Description

Example:

Bob creates a model named foo and shares it with another user, Mary, an entry will be placed in Mary's models.yaml with the model name and UUID.

If Bob deletes the model foo, and create a new one with the same name, Mary will not be able to use the new model and will get this error when running juju status:

$juju status
WARNING discarding API open error: connecting with cached addresses: unknown model: "157c8ba8-ffe9-4e69-834e-9035aea1db96" (not found)
ERROR connecting with bootstrap config: unknown model: "157c8ba8-ffe9-4e69-834e-9035aea1db96" (not found)

Running switch again doesn't help:
$ juju switch amazon:foo
local.amazon:foo (no change)

You can work around this by manually deleting the model information from the models.yaml file.

tags: added: usability
Changed in juju-core:
milestone: none → 2.0.0
affects: juju-core → juju
Changed in juju:
milestone: 2.0.0 → none
milestone: none → 2.0.0
Curtis Hovey (sinzui) on 2016-10-06
Changed in juju:
milestone: 2.0.0 → 2.0.1
Curtis Hovey (sinzui) on 2016-11-01
Changed in juju:
milestone: 2.0.1 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers