adding machine after destroying another fails

[Adam Stokes]

New machines can not be added once one is deleted.

Env: local
Version: 1.20.9-trusty-amd64
Distro: trusty

reproducer:

~/.juju/environments.yaml

default: local

environments:
  local:
    type: local
    lxc-clone: true
    default-series: trusty

$ juju bootstrap
$ juju add-machine
$ juju destroy-machine 1
$ juju add-machine

1) Bootstrap succeeds
2) machine addition succeeds
3) destroy machine succeeds
4) add machine fails to bring up the machine into a started state even though lxc-ls shows the machine as running

$ sudo lxc-ls -f

NAME STATE IPV4 IPV6 AUTOSTART
--------------------------------------------------------------
adam-local-machine-2 RUNNING 10.0.3.225 - YES
juju-trusty-lxc-template STOPPED - - NO

Interesting error in `machine-1` log (why no machine-2 log created even though its machine 2 thats having the problem?)

machine-1: 2014-10-12 16:29:19 DEBUG juju.worker.logger logger.go:45 reconfiguring logging from "<root>=DEBUG" to "<root>=WARNING;unit=DEBUG"
machine-1: 2014-10-12 16:29:19 WARNING juju.cmd.jujud machine.go:381 determining kvm support: INFO: /dev/kvm does not exist
machine-1: HINT: sudo modprobe kvm_intel
machine-1: modprobe: ERROR: ../libkmod/libkmod.c:556 kmod_search_moddep() could not open moddep file '/lib/modules/3.13.0-35-generic/modules.dep.bin'
machine-1: : exit status 1
machine-1: no kvm containers possible
machine-0: 2014-10-12 16:30:08 ERROR juju.rpc server.go:554 error writing response: EOF

$ juju status

environment: local
machines:
  "0":
    agent-state: started
    agent-version: 1.20.9.1
    dns-name: localhost
    instance-id: localhost
    series: trusty
    state-server-member-status: has-vote
  "2":
    agent-state: pending
    instance-id: adam-local-machine-2
    series: trusty
    hardware: arch=amd64
services: {}

Attaching all-machines.log which never shows any log information from machine-2. Wrt 'nov kvm containers possible'
the log actually shows kvm available initially but then spits this error out once we delete and attempt to add a second
machine.

Note that doing a `juju destroy-machine 2` will never destroy the machine I have to append a `--force`.

I went as far as killing jujud for machine 0 and juju-mongod and letting those processes restart themsevles.

Only thing that works is destroying the environment and starting over.

[Adam Stokes (adam-stokes)]

Fails on utopic as well

1.20.8-utopic-amd64