model already exists but can't be destroyed because it's not found - lots of "lease manager stopped" errors
Bug #1593394 reported by
Jason Hobbs
This bug report is a duplicate of:
Bug #1591387: juju controller stuck in infinite loop during teardown - "lease manager stopped" errors.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Triaged
|
High
|
Unassigned |
Bug Description
I destroyed a model and then tried to add it again (wanted to clear out all the services to redeploy it from scratch).
It's now stuck in a state where I can neither add it nor destroy it because when I try to add it, sit says it doesn't exist, but when I try to destroy it, it says it's not found.
http://
It's been like this for about 5 minutes.
This is with 2.0-beta8-
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
summary: |
- model already exists but can't be destroyed because it's not found + model already exists but can't be destroyed because it's not found - + lots of "lease manager stopped" errors |
To post a comment you must log in.
Can you attach / paste the following?
1 - Output from `juju status -m dual-region --format=yaml`
2 - /var/log/ juju/machine- 0.log from machine 0 in the controller model