| 2013-09-02 16:20:21 |
Kurt |
bug |
|
|
added bug |
| 2013-09-25 21:45:06 |
Curtis Hovey |
summary |
Cannot destroy service in 1.12 |
Cannot destroy service when install hook failed |
|
| 2013-09-25 21:45:09 |
Curtis Hovey |
juju-core: status |
New |
Triaged |
|
| 2013-09-25 21:45:13 |
Curtis Hovey |
juju-core: importance |
Undecided |
High |
|
| 2013-09-25 21:47:16 |
Curtis Hovey |
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.
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.
EDIT: This was also seen deploying to canonistack with one service per node.
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 |
|
| 2013-10-09 04:09:05 |
Curtis Hovey |
tags |
|
canonical-webops-juju |
|
| 2013-10-09 04:10:31 |
Curtis Hovey |
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.
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.
EDIT: This was also seen deploying to canonistack with one service per node.
EDIT: @deej: With juju1.14.1-precise-amd64 if a service agent is stuck in the pending state, for example due to an error in installing the charm, that service is essentially unkillable. The service agent clearly appears to know it should be dying but never actually gets to the point where it can die.
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 |
|
| 2013-10-11 20:30:39 |
Curtis Hovey |
tags |
canonical-webops-juju |
canonical-webops |
|
| 2013-10-12 17:21:04 |
Curtis Hovey |
tags |
canonical-webops |
canonical-webops destroy-service |
|
| 2013-11-15 12:46:55 |
Jason Robinson |
bug |
|
|
added subscriber Jason Robinson |
| 2013-11-15 14:08:20 |
Marco Ceppi |
nominated for series |
|
juju-core/docs |
|
| 2013-11-15 14:08:20 |
Marco Ceppi |
bug task added |
|
juju-core/docs |
|
| 2013-11-15 14:08:29 |
Marco Ceppi |
juju-core/docs: status |
New |
In Progress |
|
| 2013-11-15 14:08:33 |
Marco Ceppi |
juju-core/docs: importance |
Undecided |
High |
|
| 2013-11-15 14:08:37 |
Marco Ceppi |
juju-core/docs: assignee |
|
Marco Ceppi (marcoceppi) |
|
| 2013-11-15 15:00:53 |
Marco Ceppi |
juju-core/docs: status |
In Progress |
Fix Committed |
|
| 2013-11-17 05:55:12 |
Matt Rae |
bug |
|
|
added subscriber Matt Rae |
| 2013-11-19 13:39:15 |
Nick Veitch |
juju-core/docs: status |
Fix Committed |
Fix Released |
|
| 2014-03-04 11:07:03 |
Ryan Finnie |
tags |
canonical-webops destroy-service |
canonical-is canonical-webops destroy-service |
|
| 2014-03-04 11:07:16 |
Ryan Finnie |
bug |
|
|
added subscriber The Canonical Sysadmins |
| 2014-05-12 18:10:38 |
Canonical Juju QA Bot |
juju-core: importance |
High |
Medium |
|
| 2016-07-31 21:39:21 |
Anastasia |
juju-core: importance |
Medium |
High |
|
| 2016-08-08 01:41:23 |
Anastasia |
nominated for series |
|
juju-core/1.25 |
|
| 2016-08-08 01:41:23 |
Anastasia |
bug task added |
|
juju-core/1.25 |
|
| 2016-08-08 01:41:31 |
Anastasia |
juju-core/1.25: status |
New |
Won't Fix |
|
| 2016-08-08 01:41:36 |
Anastasia |
juju-core: status |
Triaged |
Incomplete |
|
| 2016-11-17 00:13:53 |
Anastasia |
juju-core: status |
Incomplete |
Won't Fix |
|
