** Description changed: In the maas user prefs page it says "You'll need a separate MAAS key for each Juju environment" but this is not of the slightest use since the API for returning owned nodes filters only on the user. One thing we could do is also take into account the API key used to access the API and only return nodes based on the owner/key combo. Related bugs: * 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 1229275: juju destroy-environment also destroys nodes that are not controlled by juju + + [Impact] + This causes that 2 admin users cannot have their own separate environment, causing them to conflict between environments, and also destroy machines that are not controller by a one environment, but rather, all machines being deployed. + + [Test Case] + 1. Install maas + 2. Create to admin users + 3. Try to use both to deploy different juju environments. + + [Regression Potential] + Minimal. The provided fix allows multiple juju environments to work, without affecting current single juju 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/1239488 Title: [SRU] Juju api client cannot distinguish between environments To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1239488/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
