Local provider isn't usable after an old environment has been destroyed

I would expect that when using the local provider, if I do 'sudo juju destroy-environment',
I can create a new local environment using 'sudo juju bootstrap'. But it doesn't seem
that works.

Let's say that I do some testing with a local provider, and I decide to start over, so I
do "sudo juju destroy-environment"

Now when I do "sudo juju bootstrap", the bootstrap itself doesn't return any error,
but looking at "juju status" after I've deployed a new service I see this:

environment: local
machines:
  "0":
    agent-state: started
    agent-version: 1.15.1.1
    dns-name: 10.0.3.1
    instance-id: localhost
    series: saucy
  "1":
    agent-state-info: '(error: container "bjorn-local-machine-1" is already created)'
    instance-id: pending
    series: precise
services:
  mysql:
    charm: cs:precise/mysql-27
    exposed: false
    relations:
      cluster:
      - mysql
    units:
      mysql/0:
        agent-state: pending
        machine: "1"

Ok, so I have to manually remove the containers, using lxc-destroy. However, that also
isn't enough, now after a new bootstrap and deploy I see this:
machines:
  "0":
    agent-state: started
    agent-version: 1.15.1.1
    dns-name: 10.0.3.1
    instance-id: localhost
    series: saucy
  "1":
    agent-state-info: '(error: symlink /var/lib/lxc/bjorn-local-machine-1/config /etc/lxc/auto/bjorn-local-machine-1.conf:
      file exists)'
    instance-id: pending
    series: precise
services:
  mysql:
    charm: cs:precise/mysql-27
    exposed: false
    relations:
      cluster:
      - mysql
    units:
      mysql/0:
        agent-state: pending
        machine: "1"