Currently when doing a plan update using the UI, the tarball / files are uploaded as they are to Swift. This means if the update contains a plan-environment.yaml file (e.g. the default, minimal one [1]), user-set parameters will be overridden.
This can be a desirable feature since it allows importing deployment details. Also, the UI doesn't handle upgrades so it's not an issue from this side either.
jtomasek suggested we might want to merge the plan-environment.yaml sections, however this opens up new issues around how to handle the removal of parameters or environments (the CLI is also struggling with this and for now resorts to resetting the parameters and reprocessing them from the templates, also cf. bug 1623431 still open).
[1] https://github.com/openstack/tripleo-heat-templates/blob/master/plan-environment.yaml
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
Valid example: CONFIRMED FOR: FUTURE