juju destroy-machine is incompatible in trunk vs 1.16
Bug #1253643 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
John A Meinel | ||
| 1.16 |
Fix Released
|
Critical
|
John A Meinel | ||
| juju-core (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Saucy |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
[Impact]
juju clients < 1.16.4 can't destroy machines in environments >= 1.16.4
[Test Case]
with a juju-core client < 1.16.4 (from release pocket)
juju deploy mysql
juju remove-unit mysql/0
juju terminate-machine 1
[Regression Potential]
Minimal, part of upstream 1.16.6 release, impact limited to destroy-machines code paths.
[Original bug report]
juju destroy-machine uses client.
As this doesn't exist in 1.16 we can't destroy-machines against 1.16
part of bug #1253619
Related branches
lp:~jameinel/juju-core/1.16-destroy-machine-compat-1253643
- Juju Engineering: Pending requested
-
Diff: 89 lines (+58/-3)1 file modifiedcmd/juju/destroymachine.go (+58/-3)
| description: | updated |
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in juju-core: | |
| assignee: | nobody → John A Meinel (jameinel) |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| milestone: | 1.17.1 → 1.17.0 |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| Changed in juju-core (Ubuntu): | |
| status: | New → Fix Released |
| description: | updated |
| description: | updated |
Revision history for this message
| Rolf Leggewie (r0lf) wrote | #2 |
| Changed in juju-core (Ubuntu Saucy): | |
| status: | New → Won't Fix |
To post a comment you must log in.
DestroyMachine got added into the 1.16 branch (for the 1.16.4 release), so this becomes critical there if we want to actually do another 1.16 release (which we appear to need for the backup/restore work).