harvest mode setting not honoured by destroy-model
Bug #1671733 reported by
Frode Nordahl
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
$ juju --version
2.2-alpha1-
Steps to reproduce:
1) juju add-model test
2) juju add-machine
3) juju model-config provisioner-
4) juju remove-machine 0
5) Verify that machine has been removed from model
6) Verify that machine has NOT been harvested on the provider
7) juju destroy-model test
8) Watch that regardless of model-config provisioner-
tags: | added: sts |
tags: | added: destroy-machine destroy-model harvest |
tags: | added: teardown |
Changed in juju: | |
milestone: | 2.6.1 → 2.6.2 |
Changed in juju: | |
milestone: | 2.6.2 → 2.6.3 |
Changed in juju: | |
milestone: | 2.6.3 → 2.6.4 |
Changed in juju: | |
status: | In Progress → Triaged |
milestone: | 2.6.4 → 2.7-beta1 |
Changed in juju: | |
milestone: | 2.7-beta1 → 2.7-rc1 |
Changed in juju: | |
milestone: | 2.7-rc1 → none |
To post a comment you must log in.
The lifetimes of machines deployed by Juju are intentionally tied to the
lifetime of the model. We don't support identifying already running
machines which means that those machines would just become orphaned and it
would not be possible to control them under Juju again.
Harvest mode was never intended to support this. Is there a concrete reason
why you want to deploy but never operate those machines afterward?
Tempted to flag this as invalid/won't fix
John
=:->
On Mar 10, 2017 09:55, "Frode Nordahl" <email address hidden> wrote:
> ** Tags added: sts /bugs.launchpad .net/bugs/ 1671733 /bugs.launchpad .net/juju/ +bug/1671733/ +subscriptions
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https:/
>
> Title:
> harvest mode setting not honoured by destroy-model
>
> To manage notifications about this bug go to:
> https:/
>