Comment 3 for bug 1217781

Revision history for this message
Matt Rae (mattrae) wrote :

Hi I'm using juju 1.16.2 and machines that never came up are still do not get terminated. They stay in the 'dying' state forever (over night at least).

$ juju -v bootstrap
$ juju status
environment: maas
machines:
"0":
agent-state: started
agent-version: 1.16.2
dns-name: node1001.cloud
instance-id: /MAAS/api/1.0/nodes/node-70cc4f36-3730-11e3-a5f3-525400c5247e/
series: precise
services: {}
$ juju deploy ubuntu

# now power off the machine that was allocated at some point before the machine agent comes up.

$ juju destroy-service ubuntu
$ juju terminate-machine 1
$ juju status
environment: maas
machines:
"0":
agent-state: started
agent-version: 1.16.2
dns-name: node1001.cloud
instance-id: /MAAS/api/1.0/nodes/node-70cc4f36-3730-11e3-a5f3-525400c5247e/
series: precise
"1":
agent-state: pending
dns-name: node1003.cloud
instance-id: /MAAS/api/1.0/nodes/node-77bece04-3730-11e3-a5f3-525400c5247e/
life: dying
series: precise
services: {}

$ apt-cache policy juju-core
juju-core:
Installed: 1.16.2-0ubuntu1~ubuntu12.04.1~juju1
Candidate: 1.16.2-0ubuntu1~ubuntu12.04.1~juju1
Version table:
*** 1.16.2-0ubuntu1~ubuntu12.04.1~juju1 0
500 http://ppa.launchpad.net/juju/stable/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status
1.16.0-0ubuntu1~ctools1 0
500 http://10.0.0.1/ubuntu-cloud/ubuntu/ precise-updates/cloud-tools/main amd64 Packages

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.3 LTS
Release: 12.04
Codename: precise