** Tags added: maas
** Summary changed:
- juju destroy-environment also destroys nodes that are not controlled by juju
+ [maas] juju destroy-environment also destroys nodes that are not controlled
by juju
** Changed in: juju
Importance: Undecided = High
--
You received this bug
** 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
Looks like we never added anything to tag the machines with their
environment.
Implementation note: *please* tag with environment UUID, not environment
name (names are not globally unique, and environments will be
referencing one another one day: treating the name as anything other
than an alias
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
** Also affects: juju
Importance: Undecided
Status: New
--
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:
juju destroy-environment also destroys nodes that are
** Changed in: juju
Status: New = Confirmed
--
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:
juju destroy-environment also destroys nodes that are not controlled
This might be a bug in the maas provider of juju-core… it definitely
needs investigation…
--
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:
juju destroy-environment also
