panic on destroy-environment with local provider

[Andrew Wilkins]

Bootstrapped local at git commit 99f95aa71e6cabc56c34c58b835f45491e6eeb86, did some things (deployed a unit with storage; don't think this is relevant), and then attempted to destroy the env. I got a panic:
    http://paste.ubuntu.com/12303686/

Running Ubuntu 15.04.

[Jesse Meek (waigani)]

The following worked for me:

$ git checkout 99f95aa
$ make install
$ juju bootstrap
$ juju deploy cs:~axwalk/postgresql --storage data=rootfs
$ juju destroy-environment -y local

Note, the postgresql unit failed to initialize:

 units:
      postgresql/0:
        workload-status:
          current: unknown
          message: agent is lost, sorry! See 'juju status-history postgresql/0'
          since: 07 Sep 2015 15:40:44+12:00
        agent-status:
          current: lost
          message: agent is not communicating with the server

I also destroyed an environment with the ubuntu charm deployed and an empty environment.

[Andrew Wilkins (axwalk)]

Jesse, one thing I should have noted is that it does not happen every time. So absence of a panic unfortunately does not prove lack of a bug here.

[Cheryl Jennings (cherylj)]

Marking as invalid for core as the local provider was removed in 2.0.