One solution to fix this problem would be this:
- when the env is bootstrapped: create a tag named after the environment UUID
- each time juju takes control of a node: associate that tag with the node
- when juju fetches the list of instances it controls, only return the nodes
associated with that tag
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Importance: Undecided => Critical
** Changed in: juju-core
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1229275
Title:
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-core/+bug/1229275/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
