Can't destroy service -- juju status "failed" & unknown relation 0 error in log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Medium
|
Unassigned |
Bug Description
Juju 2.0, built from master at 0bd48e6.
Steps to reproduce:
I deployed an etcd charm with 3 units, related it to prometheus, everything worked, no problem.
Did `juju destroy-service etcd` and two of the etcd units died and went away. However, one of them is stuck and repeated `juju destroy-service etcd` commands do not remove it.
The unit agent log on the stuck unit shows:
2016-05-13 13:32:41 INFO juju.worker.uniter resolver.go:120 committing "relation-broken" hook
2016-05-13 13:32:42 INFO juju.worker.uniter uniter.go:355 unit "etcd/2" shutting down: committing operation "skip run relation-broken (0) hook": unknown relation: 0
2016-05-13 13:32:42 ERROR juju.worker.
2016-05-13 13:32:42 INFO juju.worker.
2016-05-13 13:32:45 INFO worker.uniter.jujuc tools.go:20 ensure jujuc symlinks in /var/lib/
2016-05-13 13:32:45 INFO worker.uniter.jujuc tools.go:40 was a symlink, now looking at /var/lib/
2016-05-13 13:32:45 INFO juju.worker.
2016-05-13 13:32:45 INFO juju.worker.
2016-05-13 13:32:45 INFO juju.worker.uniter uniter.go:164 unit "etcd/2" started
2016-05-13 13:32:45 INFO juju.worker.uniter uniter.go:203 hooks are retried true
2016-05-13 13:32:45 INFO juju.worker.uniter resolver.go:120 committing "relation-broken" hook
2016-05-13 13:32:45 INFO juju.worker.uniter uniter.go:355 unit "etcd/2" shutting down: committing operation "skip run relation-broken (0) hook": unknown relation: 0
2016-05-13 13:32:45 ERROR juju.worker.
2016-05-13 13:32:48 INFO worker.uniter.jujuc tools.go:20 ensure jujuc symlinks in /var/lib/
2016-05-13 13:32:48 INFO worker.uniter.jujuc tools.go:40 was a symlink, now looking at /var/lib/
2016-05-13 13:32:48 INFO juju.worker.
2016-05-13 13:32:48 INFO juju.worker.
2016-05-13 13:32:48 INFO juju.worker.uniter uniter.go:164 unit "etcd/2" started
2016-05-13 13:32:48 INFO juju.worker.uniter uniter.go:203 hooks are retried true
2016-05-13 13:32:48 INFO juju.worker.uniter resolver.go:120 committing "relation-broken" hook
2016-05-13 13:32:48 INFO juju.worker.uniter uniter.go:355 unit "etcd/2" shutting down: committing operation "skip run relation-broken (0) hook": unknown relation: 0
2016-05-13 13:32:48 ERROR juju.worker.
2016-05-13 13:32:51 INFO worker.uniter.jujuc tools.go:20 ensure jujuc symlinks in /var/lib/
2016-05-13 13:32:51 INFO worker.uniter.jujuc tools.go:40 was a symlink, now looking at /var/lib/
2016-05-13 13:32:51 INFO juju.worker.
2016-05-13 13:32:51 INFO juju.worker.
2016-05-13 13:32:51 INFO juju.worker.uniter uniter.go:164 unit "etcd/2" started
2016-05-13 13:32:51 INFO juju.worker.uniter uniter.go:203 hooks are retried true
2016-05-13 13:32:51 INFO juju.worker.uniter resolver.go:120 committing "relation-broken" hook
2016-05-13 13:32:51 INFO juju.worker.uniter uniter.go:355 unit "etcd/2" shutting down: committing operation "skip run relation-broken (0) hook": unknown relation: 0
2016-05-13 13:32:51 ERROR juju.worker.
Changed in juju-core: | |
status: | Incomplete → New |
Changed in juju-core: | |
importance: | Undecided → Medium |
status: | New → Triaged |
affects: | juju-core → juju |
I'm able to recover from this condition with `juju remove-machine --force`, but that `unknown relation: 0` error is probably indicative of some problems.