Comment 4 for bug 1384001

Something similar happened to the landscape cloud installer. I started a deployment, and decided to abort it as soon as the bootstrap node was up. Landscape then issues a juju destroy-environment call, and that failed with this error:

ERROR destroying environment: gomaasapi: got error back from server: 500 INTERNAL SERVER ERROR (Unable to change power state to 'off' for node shawmut: another action is already in progress for that node.)

Landscape then tried again with --force, which got the same error, and gave up.

The end result is that the nodes stayed allocated in MAAS, effectively having "leaked" due to this error. They are even all "deployed" now.

I will attach some logs and a screenshot.