juju destroy-environment released machines not deployed by juju

It removed a machine deployed by another user, which was a non-root user

I just spoke with Andres, and wanted to clarify how to reproduce the unexpected behavior seen here:

(1) Deploy a machine manually
(2) Deploy with Juju
(3) destroy-environment

Expected behavior: only the Juju environment will be torn down

Actual behavior: All manually deployed systems are torn down along with the Juju environment

I can't reproduce this problem: I'm using the latest MAAS 1.8 and Juju 1.22.1-0ubuntu1~14.04.1~juju1 (from the stable PPA).
I've got two machines: one deployed (using the UI) by a non-admin user and one deployed (by Juju). Destroying the environment only released the machine deployed with Juju. The other one was left un-touched.

btw, any reason why you added a bug task for *py*juju on this bug?

Try using --force, does that make any difference?? Pyjuju probably a
mistake.
On Apr 23, 2015 5:45 AM, "Raphaël Badin" <email address hidden> wrote:

> btw, any reason why you added a bug task for *py*juju on this bug?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1445990
>
> Title:
> juju destroy-environment released machines not deployed by juju
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1445990/+subscriptions
>

I tried with --force: no difference: everything went fine.