Missing relation in model teardown
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
During the destruction of a very large testing model, the system got itself a little blocked
$ juju status
Model Controller Cloud/Region Version SLA Timestamp Notes
default raft-test aws/us-east-1 2.8.1.1 unsupported 19:24:58+12:00 attempt 292 to destroy model failed (will retry): model not empty, found 1 machine, 2 applications (model not empty)
App Version Status Scale Charm Store Rev OS Notes
primary 18.04 terminated 0/1 ubuntu-lite jujucharms 7 ubuntu
sub4 6.8.9 waiting 0 filebeat jujucharms 25 ubuntu
Unit Workload Agent Machine Public address Ports Message
primary/0* terminated executing 0 34.200.233.197 (remove)
sub4/0* waiting failed 34.200.233.197 Waiting for: elasticsearch, logstash or kafka.
Machine State DNS Inst id Series AZ Message
0 stopped 34.200.233.197 i-0f9a9f3e9c1e2897f bionic us-east-1a running
Looking at the logs for the model, we see this:
$ juju debug-log
unit-sub4-0: 19:21:04 INFO juju.worker.uniter unit "sub4/0" shutting down: committing operation "skip run relation-broken (3; app: ) hook": unknown relation: 3
unit-sub4-0: 19:21:04 ERROR juju.worker.
unit-sub4-0: 19:23:11 INFO juju.agent.tools ensure jujuc symlinks in /var/lib/
unit-sub4-0: 19:23:11 INFO juju.agent.tools was a symlink, now looking at /var/lib/
unit-sub4-0: 19:23:11 INFO juju.worker.uniter unit "sub4/0" started
unit-sub4-0: 19:23:11 INFO juju.worker.uniter hooks are retried true
unit-sub4-0: 19:23:11 INFO juju.worker.uniter committing "relation-broken" hook
unit-sub4-0: 19:23:11 ERROR juju.worker.uniter resolver loop error: committing operation "skip run relation-broken (3; app: ) hook": unknown relation: 3
unit-sub4-0: 19:23:11 INFO juju.worker.uniter unit "sub4/0" shutting down: committing operation "skip run relation-broken (3; app: ) hook": unknown relation: 3
unit-sub4-0: 19:23:11 ERROR juju.worker.
unit-sub4-0: 19:25:22 INFO juju.agent.tools ensure jujuc symlinks in /var/lib/
unit-sub4-0: 19:25:22 INFO juju.agent.tools was a symlink, now looking at /var/lib/
unit-sub4-0: 19:25:22 INFO juju.worker.uniter unit "sub4/0" started
unit-sub4-0: 19:25:22 INFO juju.worker.uniter hooks are retried true
unit-sub4-0: 19:25:22 INFO juju.worker.uniter committing "relation-broken" hook
unit-sub4-0: 19:25:22 ERROR juju.worker.uniter resolver loop error: committing operation "skip run relation-broken (3; app: ) hook": unknown relation: 3
unit-sub4-0: 19:25:22 INFO juju.worker.uniter unit "sub4/0" shutting down: committing operation "skip run relation-broken (3; app: ) hook": unknown relation: 3
unit-sub4-0: 19:25:22 ERROR juju.worker.
The uniter worker was just bouncing failing to progress with an unknown relation.
| Tim Penhey (thumper) wrote | #1 |
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| importance: | High → Low |
| tags: | added: expirebugs-bot |
This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.