[Bug 1229275] Re: [maas] juju destroy-environment also destroys nodes that are not controlled by juju

[Scott Moser]

** Description changed:

  In a saucy MAAS environment, I had machines allocated to the admin user
  that were deployed using maas-cli (not using juju). These were perfectly
  running machines. However, while trying to use juju I noticed that a
  'juju destroy-environment' put the machines that were 'allocated to
  admin' back to a 'Ready' state. These machines were not being used /
  controller by juju, but rather by maas-cli.
  
  This means that juju destroys all of the machines regardless of whether
  they are being used by juju or not.
  
  Related bugs:
-  bug 1081247:  maas provider releases all nodes it did not allocate [does not play well with others]
+  * bug 1237398: "You'll need a separate MAAS key for each Juju environment" is wrong.
+  * bug 1081247: maas provider releases all nodes it did not allocate [does not play well with others]
+  * bug 1239488: Juju api client cannot distinguish between environments

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1229275

Title:
  [maas] juju destroy-environment also destroys nodes that are not
  controlled by juju

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1229275/+subscriptions