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.
kurt@maas-cntrl:~/deployment$ juju destroy-unit rabbitmq-server/0 --debug
2013-09-02 16:09:01 DEBUG juju.environs.maas environprovider.go:27 opening environment "maas".
2013-09-02 16:09:01 DEBUG juju state.go:138 waiting for DNS name(s) of state server instances [/MAAS/api/1.0/nodes/node-9c81fa82-1182-11e3-820f-000c2969475a/]
2013-09-02 16:09:01 INFO juju open.go:69 state: opening state; mongo addresses: ["ptqkd.master:37017"]; entity ""
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-cntrl:~/deployment$ juju -v status
2013-09-02 16:19:24 INFO juju open.go:69 state: opening state; mongo addresses: ["ptqkd.master:37017"]; entity ""
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/1.0/nodes/node-9c81fa82-1182-11e3-820f-000c2969475a/
series: precise
services:
juju-gui:
charm: cs:precise/juju-gui-76
exposed: true
units:
juju-gui/0: agent-state: started agent-version: 1.12.0
machine: "0" public-address: ptqkd.master
mysql:
charm: cs:precise/mysql-27
exposed: false
relations:
cluster:
- mysql
units:
mysql/0: agent-state: error agent-state-info: 'hook failed: "config-changed"' agent-version: 1.12.0
machine: "0" public-address: ptqkd.master
rabbitmq-server:
charm: cs:precise/rabbitmq-server-14
exposed: false
life: dying
units:
rabbitmq-server/0: agent-state: error agent-state-info: 'hook failed: "install"' agent-version: 1.12.0
life: dying
machine: "0" public-address: ptqkd.master
2013-09-02 16:19:24 INFO juju supercommand.go:237 command finished
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.
kurt@maas- cntrl:~ /deployment$ juju destroy-unit rabbitmq-server/0 --debug .go:27 opening environment "maas". api/1.0/ nodes/node- 9c81fa82- 1182-11e3- 820f-000c296947 5a/] master: 37017"] ; entity "" cntrl:~ /deployment$ juju -v status master: 37017"] ; entity "" 1.0/nodes/ node-9c81fa82- 1182-11e3- 820f-000c296947 5a/ juju-gui- 76
agent- state: started
agent- version: 1.12.0
public- address: ptqkd.master
agent- state: error
agent- state-info: 'hook failed: "config-changed"'
agent- version: 1.12.0
public- address: ptqkd.master rabbitmq- server- 14 server/ 0:
agent- state: error
agent- state-info: 'hook failed: "install"'
agent- version: 1.12.0
public- address: ptqkd.master
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