Cannot destroy service when install hook failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
High
|
Unassigned | ||
1.25 |
Won't Fix
|
Undecided
|
Unassigned | ||
Docs |
Fix Released
|
High
|
Marco Ceppi |
Bug Description
So far this has only happened when deploying multiple services to a single node (with maas). When I see that a service such as rabbitmq-server fails to deploy successfully and go to destroy the service, the command appears to return with no errors, but the service is not removed. juju status shows the service is still on the host and has a status showing "life: dying". This never goes away.
EDIT: This was also seen deploying to canonistack with one service per node.
EDIT: @deej: With juju1.14.
kurt@maas-
2013-09-02 16:09:01 DEBUG juju.environs.maas environprovider
2013-09-02 16:09:01 DEBUG juju state.go:138 waiting for DNS name(s) of state server instances [/MAAS/
2013-09-02 16:09:01 INFO juju open.go:69 state: opening state; mongo addresses: ["ptqkd.
2013-09-02 16:09:01 INFO juju open.go:107 state: connection established
2013-09-02 16:09:01 INFO juju supercommand.go:237 command finished
kurt@maas-
2013-09-02 16:19:24 INFO juju open.go:69 state: opening state; mongo addresses: ["ptqkd.
2013-09-02 16:19:24 INFO juju open.go:107 state: connection established
machines:
"0":
agent-state: started
agent-version: 1.12.0
dns-name: ptqkd.master
instance-id: /MAAS/api/
series: precise
services:
juju-gui:
charm: cs:precise/
exposed: true
units:
juju-gui/0:
machine: "0"
mysql:
charm: cs:precise/mysql-27
exposed: false
relations:
cluster:
- mysql
units:
mysql/0:
machine: "0"
rabbitmq-server:
charm: cs:precise/
exposed: false
life: dying
units:
rabbitmq-
life: dying
machine: "0"
2013-09-02 16:19:24 INFO juju supercommand.go:237 command finished
tags: | added: canonical-webops-juju |
description: | updated |
tags: |
added: canonical-webops removed: canonical-webops-juju |
tags: | added: destroy-service |
tags: | added: canonical-is |
Changed in juju-core: | |
importance: | High → Medium |
Changed in juju-core: | |
importance: | Medium → High |
Changed in juju-core: | |
status: | Incomplete → Won't Fix |
From @Aaron's duplicate
If the initial install failed, destroy-service does not work, but does not report that it isn't working.
$ juju destroy-service jenkins jenkins- 2
agent- state: error
agent- state-info: 'hook failed: "install"'
agent- version: 1.12.0
public- address: 10.55.32.32
$ juju status
...
services:
jenkins:
charm: local:precise/
exposed: true
life: dying
units:
jenkins/0:
life: dying
machine: "1"
This went on until I destroyed the environment.
Later on, I determined that I could work around the issue by doing "juju resolve" first, before "juju destroy-service".