1.25.6 "ERROR juju.worker.uniter.filter filter.go:137 tomb: dying"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Critical
|
Unassigned | ||
1.25 |
Fix Released
|
Critical
|
Unassigned |
Bug Description
After destroying the only unit in a service and re-deploying a new one with a new charm revision, I got a lot of the following in the unit log:
==> unit-prometheus
2016-08-16 08:33:38 ERROR juju.worker.
2016-08-16 08:33:41 ERROR juju.worker.
2016-08-16 08:33:44 ERROR juju.worker.
2016-08-16 08:33:48 ERROR juju.worker.
2016-08-16 08:33:51 ERROR juju.worker.
2016-08-16 08:33:54 ERROR juju.worker.
2016-08-16 08:33:58 ERROR juju.worker.
No amount of restarting agents seems to un-stick this, and a subsequent hard terminate and redeploy doesn't help.
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → 1.25.7 |
milestone: | 1.25.7 → 2.0-beta17 |
importance: | Critical → High |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta17 → none |
milestone: | none → 2.0-beta17 |
Changed in juju-core: | |
importance: | Undecided → Critical |
status: | New → Triaged |
Changed in juju: | |
milestone: | 2.0-beta17 → 2.0-beta18 |
no longer affects: | juju |
tags: | added: landscape |
tags: | added: kanban-cross-team |
tags: | removed: kanban-cross-team |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
importance: | Critical → Undecided |
tags: | added: cdo-qa-blocker |
tags: | added: caonical-is |
tags: |
added: canonical-is removed: caonical-is |
Changed in juju-core: | |
status: | Won't Fix → Triaged |
importance: | Undecided → Critical |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Additional supporting logs:
http:// paste.ubuntu. com/23107655/ paste.ubuntu. com/23107656/
http://