2013-06-13 19:20:10 |
Andreas Hasenack |
bug |
|
|
added bug |
2013-06-13 19:20:33 |
Andreas Hasenack |
description |
$ juju status
machines:
"0":
agent-state: started
agent-version: 1.11.1.1
dns-name: 10.55.63.126
instance-id: 8ec63558-272c-4a2e-85bc-5f6f19c5e5c7
series: precise
"3":
agent-state: down
agent-state-info: (started)
agent-version: 1.11.1.1
instance-id: 124ca183-ab37-4b62-9d22-e951d2e44e5e
instance-state: missing
series: precise
services:
lds-quickstart:
charm: local:precise/lds-quickstart-59
exposed: true
life: dying
units:
lds-quickstart/0:
agent-state: down
agent-state-info: '(error: hook failed: "install")'
agent-version: 1.11.1.1
life: dying
machine: "3"
public-address: 10.55.63.181
But:
$ juju resolved lds-quickstart/0
error: cannot set resolved mode for unit "lds-quickstart/0": already resolved
All destroy or remove commands have no apparent effect. |
$ juju status
machines:
"0":
agent-state: started
agent-version: 1.11.1.1
dns-name: 10.55.63.126
instance-id: 8ec63558-272c-4a2e-85bc-5f6f19c5e5c7
series: precise
"3":
agent-state: down
agent-state-info: (started)
agent-version: 1.11.1.1
instance-id: 124ca183-ab37-4b62-9d22-e951d2e44e5e
instance-state: missing
series: precise
services:
lds-quickstart:
charm: local:precise/lds-quickstart-59
exposed: true
life: dying
units:
lds-quickstart/0:
agent-state: down
agent-state-info: '(error: hook failed: "install")'
agent-version: 1.11.1.1
life: dying
machine: "3"
public-address: 10.55.63.181
But:
$ juju resolved lds-quickstart/0
error: cannot set resolved mode for unit "lds-quickstart/0": already resolved
All destroy or remove commands have no apparent effect. My only way out seems to be destroying the environment. |
|
2013-06-13 19:23:10 |
Andreas Hasenack |
description |
$ juju status
machines:
"0":
agent-state: started
agent-version: 1.11.1.1
dns-name: 10.55.63.126
instance-id: 8ec63558-272c-4a2e-85bc-5f6f19c5e5c7
series: precise
"3":
agent-state: down
agent-state-info: (started)
agent-version: 1.11.1.1
instance-id: 124ca183-ab37-4b62-9d22-e951d2e44e5e
instance-state: missing
series: precise
services:
lds-quickstart:
charm: local:precise/lds-quickstart-59
exposed: true
life: dying
units:
lds-quickstart/0:
agent-state: down
agent-state-info: '(error: hook failed: "install")'
agent-version: 1.11.1.1
life: dying
machine: "3"
public-address: 10.55.63.181
But:
$ juju resolved lds-quickstart/0
error: cannot set resolved mode for unit "lds-quickstart/0": already resolved
All destroy or remove commands have no apparent effect. My only way out seems to be destroying the environment. |
To reproduce, destroy the instance while the unit is in "pending" state.
$ juju status
machines:
"0":
agent-state: started
agent-version: 1.11.1.1
dns-name: 10.55.63.126
instance-id: 8ec63558-272c-4a2e-85bc-5f6f19c5e5c7
series: precise
"3":
agent-state: down
agent-state-info: (started)
agent-version: 1.11.1.1
instance-id: 124ca183-ab37-4b62-9d22-e951d2e44e5e
instance-state: missing
series: precise
services:
lds-quickstart:
charm: local:precise/lds-quickstart-59
exposed: true
life: dying
units:
lds-quickstart/0:
agent-state: down
agent-state-info: '(error: hook failed: "install")'
agent-version: 1.11.1.1
life: dying
machine: "3"
public-address: 10.55.63.181
But:
$ juju resolved lds-quickstart/0
error: cannot set resolved mode for unit "lds-quickstart/0": already resolved
All destroy or remove commands have no apparent effect. My only way out seems to be destroying the environment. |
|
2013-06-15 20:18:42 |
William Reade |
juju-core: status |
New |
Incomplete |
|
2013-06-17 22:29:05 |
David Britton |
juju-core: status |
Incomplete |
New |
|
2013-06-17 22:31:19 |
David Britton |
juju-core: status |
New |
Confirmed |
|
2013-06-17 22:31:21 |
David Britton |
bug |
|
|
added subscriber David Britton |
2013-06-19 12:12:07 |
William Reade |
summary |
Unit in error, yet juju resolved claims it's fixed |
unit destruction depends on unit agents |
|
2013-06-19 12:24:59 |
William Reade |
description |
To reproduce, destroy the instance while the unit is in "pending" state.
$ juju status
machines:
"0":
agent-state: started
agent-version: 1.11.1.1
dns-name: 10.55.63.126
instance-id: 8ec63558-272c-4a2e-85bc-5f6f19c5e5c7
series: precise
"3":
agent-state: down
agent-state-info: (started)
agent-version: 1.11.1.1
instance-id: 124ca183-ab37-4b62-9d22-e951d2e44e5e
instance-state: missing
series: precise
services:
lds-quickstart:
charm: local:precise/lds-quickstart-59
exposed: true
life: dying
units:
lds-quickstart/0:
agent-state: down
agent-state-info: '(error: hook failed: "install")'
agent-version: 1.11.1.1
life: dying
machine: "3"
public-address: 10.55.63.181
But:
$ juju resolved lds-quickstart/0
error: cannot set resolved mode for unit "lds-quickstart/0": already resolved
All destroy or remove commands have no apparent effect. My only way out seems to be destroying the environment. |
The command sequence:
$ juju deploy foo
$ juju deploy-service foo
...can have surprising consequences, as follows:
* foo/0 will persist, apparently "alive", until it's deployed; only at that point will it
be destroyed (because the unit agent checks the service).
* if a new machine were created to hold foo/0, and provisioning failed for that machine,
the unit will never be destroyed (except manually, via `destroy-unit`).
* if the unit agent was previously running, but the machine agent went away unexpectedly,
the unit can never be destroyed at all (lp:1089289).
In all these cases, the impact is that the foo service gets "stuck" for longer than it should, waiting on the unit agent. By slightly tweaking service destruction, we can automatically destroy all units; this will trigger existing short-circuit paths and resolve the first two consequences, and move us a step towards a simple fix for the third. |
|
2013-06-19 12:28:56 |
William Reade |
juju-core: status |
Confirmed |
Triaged |
|
2013-06-19 12:28:59 |
William Reade |
juju-core: importance |
Undecided |
Critical |
|
2013-06-19 12:29:03 |
William Reade |
juju-core: assignee |
|
William Reade (fwereade) |
|
2013-06-19 18:43:04 |
Andreas Hasenack |
description |
The command sequence:
$ juju deploy foo
$ juju deploy-service foo
...can have surprising consequences, as follows:
* foo/0 will persist, apparently "alive", until it's deployed; only at that point will it
be destroyed (because the unit agent checks the service).
* if a new machine were created to hold foo/0, and provisioning failed for that machine,
the unit will never be destroyed (except manually, via `destroy-unit`).
* if the unit agent was previously running, but the machine agent went away unexpectedly,
the unit can never be destroyed at all (lp:1089289).
In all these cases, the impact is that the foo service gets "stuck" for longer than it should, waiting on the unit agent. By slightly tweaking service destruction, we can automatically destroy all units; this will trigger existing short-circuit paths and resolve the first two consequences, and move us a step towards a simple fix for the third. |
The command sequence:
$ juju deploy foo
$ juju destroy-service foo
...can have surprising consequences, as follows:
* foo/0 will persist, apparently "alive", until it's deployed; only at that point will it
be destroyed (because the unit agent checks the service).
* if a new machine were created to hold foo/0, and provisioning failed for that machine,
the unit will never be destroyed (except manually, via `destroy-unit`).
* if the unit agent was previously running, but the machine agent went away unexpectedly,
the unit can never be destroyed at all (lp:1089289).
In all these cases, the impact is that the foo service gets "stuck" for longer than it should, waiting on the unit agent. By slightly tweaking service destruction, we can automatically destroy all units; this will trigger existing short-circuit paths and resolve the first two consequences, and move us a step towards a simple fix for the third. |
|
2013-06-21 11:24:44 |
William Reade |
juju-core: status |
Triaged |
In Progress |
|
2013-07-10 18:11:18 |
William Reade |
branch linked |
|
lp:~fwereade/juju-core/cleaner-resumer-integrate |
|
2013-07-10 18:11:18 |
William Reade |
juju-core: milestone |
|
dev-docs |
|
2013-07-11 12:17:38 |
William Reade |
juju-core: milestone |
dev-docs |
1.11.3 |
|
2013-07-22 05:21:35 |
Dave Cheney |
juju-core: milestone |
1.11.3 |
1.11.4 |
|
2013-07-23 07:13:10 |
Dave Cheney |
juju-core: milestone |
1.11.4 |
1.11.5 |
|
2013-08-06 11:21:30 |
Jorge Castro |
juju-core: status |
In Progress |
Fix Committed |
|
2013-09-03 12:15:56 |
John A Meinel |
juju-core: status |
Fix Committed |
Fix Released |
|
2014-07-24 20:42:15 |
Andreas Hasenack |
tags |
|
landscape |
|