service with no units stuck in lifecycle dying
Bug #1233457 reported by
Kapil Thangavelu
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
William Reade | ||
1.16 |
Fix Released
|
Critical
|
William Reade | ||
juju-core (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Saucy |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Services will no service units get stuck in 'dying' state preventing their removal from a deployment.
[Test Case]
juju deploy mysql
juju terminate-machine --force <machineid of mysql>
juju destroy-service mysql
[Regression Potential]
Part of the upstream tested 1.16.6 release. Change looks limited to impacted code path only
[Original Report]
[Report from the field, a service with no units (previously destroyed) is stuck in lifecycle dying. Per status snippet
mysql:
charm: local:precise/
exposed:false
life: dying
relations:
cluster:
- mysql
Related branches
lp:~fwereade/juju-core/unit-remove-depart-scopes
- John A Meinel: Approve
- Ian Booth: Approve
-
Diff: 120 lines (+80/-3)3 files modifiedstate/service.go (+7/-3)
state/unit.go (+22/-0)
state/unit_test.go (+51/-0)
lp:~fwereade/juju-core/fix-1233457-for-1.16
- Juju Engineering: Pending requested
-
Diff: 120 lines (+80/-3)3 files modifiedstate/service.go (+7/-3)
state/unit.go (+22/-0)
state/unit_test.go (+51/-0)
Changed in juju-core: | |
importance: | Undecided → High |
status: | New → Triaged |
tags: | added: destroy-service |
tags: |
added: cts-cloud-review removed: cts |
Changed in juju-core: | |
milestone: | none → 1.17.0 |
tags: | added: state-server |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
milestone: | 1.17.0 → 2.0 |
Changed in juju-core: | |
importance: | High → Critical |
milestone: | 2.0 → 1.17.0 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
milestone: | 1.17.0 → 2.0 |
status: | Fix Committed → In Progress |
Changed in juju-core: | |
milestone: | 2.0 → 1.17.0 |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
importance: | Critical → High |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Changed in juju-core (Ubuntu): | |
status: | New → Fix Released |
description: | updated |
To post a comment you must log in.
poking at the underlying mongodb shows that the mysql service still has an extant relation and no units, per william on irc <fwereade> hazmat, to me the really critical thing is that one of those units apparently managed to leave scope without updating the relation doc's unitcount