Verify Plan Update doesn't clear Mistral Env

[Udi Kalifon]

When you click "Edit" on one of the plans in the manage deployments page, and then re-upload the plan directory - all the plan configuration parameters are reset. You then have to re-enter the environments you need, the needed fields for how many controllers and computes etc that you need, the passwords and so on...

[Jason E. Rist (jason-rist)]

This should probably be considered an RFE.

[Udi Kalifon (ukalifon)]

This is supposed to be supported. We don't want to force the user to upload a new plan and re-enter all the plan parameters and environments. We want to allow the user to update the plan, and currently what happens is that updating the plan is effectively the same as uploading a new one and deleting the old. This is not a low-severity bug.

[opavlenk (opavlenk)]

 since edit plan doesn't work , I suggest to raise importance of the bug to high

[Jason E. Rist (jason-rist)]

Edit in place? or Be able to upload new plan files for same plan.

[Julie Pichon (jpichon)]

Note that I'm not sure it's possible to do this with the backend at the moment, and there are a few existing issues around updating plans:

https://review.openstack.org/#/c/371468/3
https://bugs.launchpad.net/tripleo/+bug/1622683
https://bugs.launchpad.net/tripleo/+bug/1623431

The trend seems to be toward rethinking this for Ocata, and going the delete + re-create way for now.

[Udi Kalifon (ukalifon)]

Verified with the current version and this is working OK. The parameters and the environment were not lost when I re-uploaded the plan.

[Jason E. Rist (jason-rist)]

So can this be closed?

[Udi Kalifon (ukalifon)]

This can be closed.