| 2013-09-23 16:20:39 |
Andres Rodriguez |
bug |
|
|
added bug |
| 2013-09-26 09:13:04 |
William Reade |
maas (Ubuntu): status |
New |
Triaged |
|
| 2013-09-26 09:13:06 |
William Reade |
maas (Ubuntu): importance |
Undecided |
Critical |
|
| 2013-09-26 09:23:20 |
Raphaël Badin |
bug task added |
|
juju-core |
|
| 2013-09-26 09:23:36 |
Raphaël Badin |
juju-core: importance |
Undecided |
Critical |
|
| 2013-09-26 09:23:38 |
Raphaël Badin |
juju-core: status |
New |
Triaged |
|
| 2013-09-26 14:37:28 |
Raphaël Badin |
bug task added |
|
juju |
|
| 2013-09-26 18:18:01 |
Mark Ramm |
juju: status |
New |
Confirmed |
|
| 2013-09-27 18:53:17 |
Scott Moser |
description |
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. |
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] |
|
| 2013-10-02 02:27:54 |
Tim Penhey |
tags |
|
maas |
|
| 2013-10-02 02:28:05 |
Tim Penhey |
summary |
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 |
|
| 2013-10-02 02:28:12 |
Tim Penhey |
juju: importance |
Undecided |
High |
|
| 2013-10-03 19:19:46 |
David Britton |
tags |
maas |
maas theme-oil |
|
| 2013-10-03 22:39:02 |
Tim Penhey |
juju-core: assignee |
|
Tim Penhey (thumper) |
|
| 2013-10-03 22:39:05 |
Tim Penhey |
juju-core: status |
Triaged |
In Progress |
|
| 2013-10-03 22:39:34 |
Tim Penhey |
juju-core: milestone |
|
2.0 |
|
| 2013-10-10 10:46:08 |
Mark Ramm |
juju-core: milestone |
2.0 |
1.17.0 |
|
| 2013-10-12 03:42:09 |
Curtis Hovey |
juju: status |
Confirmed |
Triaged |
|
| 2013-10-12 03:46:56 |
Curtis Hovey |
juju: importance |
High |
Low |
|
| 2013-10-15 17:25:51 |
Scott Moser |
description |
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] |
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 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 |
|
| 2013-10-16 05:30:36 |
Julian Edwards |
branch linked |
|
lp:~allenap/juju-core/maas-environment-uuid-use |
|
| 2013-10-16 05:30:55 |
Julian Edwards |
branch linked |
|
lp:~julian-edwards/juju-core/maas-uuid-file-prefix |
|
| 2013-10-16 10:24:52 |
James Page |
bug task added |
|
juju-core (Ubuntu) |
|
| 2013-10-16 10:25:02 |
James Page |
nominated for series |
|
Ubuntu Saucy |
|
| 2013-10-16 10:25:02 |
James Page |
bug task added |
|
maas (Ubuntu Saucy) |
|
| 2013-10-16 10:25:02 |
James Page |
bug task added |
|
juju-core (Ubuntu Saucy) |
|
| 2013-10-16 10:25:08 |
James Page |
juju-core (Ubuntu Saucy): importance |
Undecided |
High |
|
| 2013-10-16 10:25:11 |
James Page |
juju-core (Ubuntu Saucy): status |
New |
Triaged |
|
| 2013-10-17 14:18:01 |
Curtis Hovey |
nominated for series |
|
juju-core/1.16 |
|
| 2013-10-17 14:18:01 |
Curtis Hovey |
bug task added |
|
juju-core/1.16 |
|
| 2013-10-17 14:18:13 |
Curtis Hovey |
juju-core/1.16: milestone |
|
1.16.1 |
|
| 2013-10-17 14:18:16 |
Curtis Hovey |
juju-core/1.16: importance |
Undecided |
High |
|
| 2013-10-17 14:18:20 |
Curtis Hovey |
juju-core/1.16: status |
New |
In Progress |
|
| 2013-10-17 14:18:50 |
Curtis Hovey |
juju-core/1.16: assignee |
|
Roger Peppe (rogpeppe) |
|
| 2013-10-17 15:46:44 |
Curtis Hovey |
juju-core/1.16: status |
In Progress |
Fix Committed |
|
| 2013-10-17 15:46:48 |
Curtis Hovey |
juju-core: status |
In Progress |
Fix Committed |
|
| 2013-10-24 23:23:03 |
Curtis Hovey |
tags |
maas theme-oil |
maas-provider theme-oil |
|
| 2013-10-31 01:49:54 |
Curtis Hovey |
juju-core/1.16: status |
Fix Committed |
Fix Released |
|
| 2013-10-31 18:34:38 |
Curtis Hovey |
juju-core/1.16: milestone |
1.16.1 |
1.16.2 |
|
| 2013-10-31 21:43:27 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/ubuntu/trusty/juju-core/trusty-proposed |
|
| 2013-10-31 22:23:39 |
Launchpad Janitor |
juju-core (Ubuntu): status |
Triaged |
Fix Released |
|
| 2013-11-12 16:09:45 |
James Page |
maas (Ubuntu): status |
Triaged |
Invalid |
|
| 2013-11-12 16:09:52 |
James Page |
maas (Ubuntu Saucy): status |
Triaged |
Invalid |
|
| 2013-11-15 19:20:20 |
Curtis Hovey |
branch linked |
|
lp:~rogpeppe/juju-core/454-1.16-maas-changes |
|
| 2013-11-20 21:17:07 |
Curtis Hovey |
juju-core: importance |
Critical |
High |
|
| 2013-11-20 21:17:11 |
Curtis Hovey |
juju-core/1.16: importance |
High |
Critical |
|
| 2013-11-21 10:04:12 |
James Page |
description |
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 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 |
[Impact]
juju destroy-environment destroys all machines allocated to the MAAS user being used in the environment, not just the ones owned by Juju.
[Test Case]
Allocate machines using maas-cli
juju bootstrap
juju destroy-environment
(all machines are terminated and powered off)
[Regression Potential]
The fix is limited to the MAAS provider in the codebase; so regression potential is limited in scope of provider.
[Original Bug Report]
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 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 |
|
| 2013-11-21 10:04:31 |
James Page |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2013-11-21 21:41:54 |
Brian Murray |
juju-core (Ubuntu Saucy): status |
Triaged |
Fix Committed |
|
| 2013-11-21 21:41:59 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2013-11-21 21:42:02 |
Brian Murray |
tags |
maas-provider theme-oil |
maas-provider theme-oil verification-needed |
|
| 2013-11-21 21:48:13 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/saucy-proposed/juju-core |
|
| 2013-11-22 11:17:28 |
James Page |
tags |
maas-provider theme-oil verification-needed |
maas-provider theme-oil verification-done |
|
| 2013-12-02 15:54:45 |
Launchpad Janitor |
juju-core (Ubuntu Saucy): status |
Fix Committed |
Fix Released |
|
| 2013-12-02 15:55:20 |
Stéphane Graber |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2013-12-20 17:40:28 |
Curtis Hovey |
juju-core: status |
Fix Committed |
Fix Released |
|
