juju destroy-model stuck with state changing too quickly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
Environment:
Juju 2.9.32-ubuntu-amd64
Microk8s: v1.23.6
Two VMs, one with Juju and Microk8s, the secibd with only Microk8s
Deployed a custom bundle using Juju on machine 1 to a model created on Microk8s cloud for machine 2.
Deployment failed to complete with pods repeatedly stuck in CrashLoopBackoff.
juju deploy hello-kubecon also failed with CrashLoopBackoff.
At this point I decided something must be wrong, and I attempted to destroy the model:
juju destroy-model 6c804230-
This did not complete, so I then proceeded to issue:
juju destroy-model magma-orc-
This also hung at the same point. I decided to get aggressive and
juju destroy-controller --destroy-
This too hung on the same model. I then looked at juju debug-log and saw what we all don't like to see:
updating units: state changing too quickly; try again soon
Turned on tracing: juju model-config logging-
Attached you will find:
1. juju debug-log --replay
2. juju dump-db
3. Text snippet of a failed txn
Changed in juju: | |
importance: | Undecided → High |
milestone: | none → 2.9-next |
status: | New → Triaged |
Changed in juju: | |
milestone: | 2.9-next → none |
JUJU_DEV_ FEATURE_ FLAGS=developer -mode juju dump-db > juju_dump-db.txt