Juju destroy-environment --force left unit in deployed state

[Chad Smith]

On a recent landscape deployment using MAAS (1.7.0~rc3+bzr3299-0ubuntu1~trusty1) I was able to get a node into DEPLOYED state and turned off by MAAS.

juju --version 1.20.11-trusty-amd64

Steps to reproduce:

1. juju bootstrap --upload-tools -e myenv
2. juju deploy landscape-quickstart

3. # destroy environment
juju destroy-environment -e maasbs --force
2014-11-17 23:22:04 WARNING juju.cmd.juju destroyenvironment.go:52 -e/--environment flag is deprecated in 1.18, please supply environment as a positional parameter
WARNING! this command will destroy the "maasbs" environment (type: maas)
This includes all machines, services, data and other resources.

Continue [y/N]? y
csmith@fringe:~/src/landscape/standalone-14.10-cherrypicks$ juju status -e maasbs
ERROR Unable to connect to environment "maasbs".
Please check your credentials or use 'juju bootstrap' to create a new environment.

Error details:
environment is not bootstrapped

4. MAAS UI reports that is received release request via MAAS UI log for the computer
"Node changed status — From 'Deployed' to 'Releasing'"

5. Check power state button in MAAS reports power off, state remains "Deployed"

Andreas grabbed the logs. If you want the DB dump from us just left us know which tables are needed.

[Julian Edwards (julian-edwards)]

Are you able to consistently re-create this?

[Christian Reis (kiko)]

Dupe of bug 1384001 or bug 1381619?

[Julian Edwards (julian-edwards)]

I'm not sure it's a dupe of those. Certainly related though.

[Blake Rouse (blake-rouse)]

Has this been reproduced recently? I believe this might have already been fixed with the serialization work that landed in 1.8.

[Launchpad Janitor (janitor)]

[Expired for MAAS because there has been no activity for 60 days.]