** Description changed: - juju destroy-machine uses client.DestroyMachines and - client.ForceDestroyMachines which needed a new API (DestroyMachines). + [Impact] + juju client 1. + + + [Original bug report] + juju destroy-machine uses client.DestroyMachines and client.ForceDestroyMachines which needed a new API (DestroyMachines). As this doesn't exist in 1.16 we can't destroy-machines against 1.16 part of bug #1253619
** Description changed: [Impact] - juju client 1. + 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.DestroyMachines and client.ForceDestroyMachines which needed a new API (DestroyMachines). As this doesn't exist in 1.16 we can't destroy-machines against 1.16 part of bug #1253619 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253643 Title: juju destroy-machine is incompatible in trunk vs 1.16 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1253643/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
