We were using parameters for scaling down but parameter_defaults for
scaling up. The old parameters from scale-down still persisted in the
stack and took precedence over the scaled-up parameter_defaults, so the
scaled-up values didn't propagate.
We already update parameter_defaults in the deployment plan in that same
method, so all we need to do is remove the 'parameters' part.
Change-Id: I90a195a66b15c7c9057bfb415b6a730bbd9a939c
Closes-Bug: #1641142
(cherry picked from commit fbc435ce167eae2c6ac1070be47ad9065561855b)
Reviewed: https:/ /review. openstack. org/396804 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=17fa3aed22c 040bd67a97b86c4 1f5d6e6ee8a94a
Committed: https:/
Submitter: Jenkins
Branch: stable/newton
commit 17fa3aed22c040b d67a97b86c41f5d 6e6ee8a94a
Author: Jiri Stransky <email address hidden>
Date: Fri Nov 11 16:46:28 2016 +0100
Only use parameter_defaults for scaling down
We were using parameters for scaling down but parameter_defaults for
scaling up. The old parameters from scale-down still persisted in the
stack and took precedence over the scaled-up parameter_defaults, so the
scaled-up values didn't propagate.
We already update parameter_defaults in the deployment plan in that same
method, so all we need to do is remove the 'parameters' part.
Change-Id: I90a195a66b15c7 c9057bfb415b6a7 30bbd9a939c c6ac1070be47ad9 065561855b)
Closes-Bug: #1641142
(cherry picked from commit fbc435ce167eae2