commit 02118fddf3f66c280c15b2549f07330f3a957d31
Author: Christian Schwede <email address hidden>
Date: Fri Mar 10 12:08:14 2017 +0100
Fix using old Swift rings when creating a new stack
The container to store Swift rings is not deleted when the stack is
deleted. This results in re-deploying old rings when deploying a new
stack.
This patch creates a copy of the old rings with a timestamp suffix and
removes the original object. Doing this will create new rings when
creating a new stack.
Closes-Bug: 1671783
Change-Id: Ie6363987ada9b516064c1ed3b215f809c3924393
(cherry picked from commit f82064e95a60b63c0c6a1df92a70f33158bc1a18)
Reviewed: https:/ /review. openstack. org/504886 /git.openstack. org/cgit/ openstack/ tripleo- common/ commit/ ?id=02118fddf3f 66c280c15b2549f 07330f3a957d31
Committed: https:/
Submitter: Zuul
Branch: stable/newton
commit 02118fddf3f66c2 80c15b2549f0733 0f3a957d31
Author: Christian Schwede <email address hidden>
Date: Fri Mar 10 12:08:14 2017 +0100
Fix using old Swift rings when creating a new stack
The container to store Swift rings is not deleted when the stack is
deleted. This results in re-deploying old rings when deploying a new
stack.
This patch creates a copy of the old rings with a timestamp suffix and
removes the original object. Doing this will create new rings when
creating a new stack.
Closes-Bug: 1671783 16064c1ed3b215f 809c3924393 c0c6a1df92a70f3 3158bc1a18)
Change-Id: Ie6363987ada9b5
(cherry picked from commit f82064e95a60b63