Failed res no need UpdateReplace which has nested_stack
Now update the resources in FAILED status will enter UpdateReplace
flow, but it's not fit for resources which has nested stack.
Especially for autoscaling group, if there is one or more server
were created/deleted failed, we shouldn't destroy all the servers
and then create new servers for the group while updation.
Reviewed: https:/ /review. openstack. org/130107 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=9b0a940a6f8 d06105840ce3139 789da133edb560
Committed: https:/
Submitter: Jenkins
Branch: master
commit 9b0a940a6f8d061 05840ce3139789d a133edb560
Author: huangtianhua <email address hidden>
Date: Wed Oct 22 11:22:02 2014 +0800
Failed res no need UpdateReplace which has nested_stack
Now update the resources in FAILED status will enter UpdateReplace
flow, but it's not fit for resources which has nested stack.
Especially for autoscaling group, if there is one or more server
were created/deleted failed, we shouldn't destroy all the servers
and then create new servers for the group while updation.
Change-Id: Ib53f66fe481acc 282123dc1743ef8 310456a1d69
Closes-bug: #1383618