Currently, when we delete a bay, we will delete the stack firstly,
then try to detroy the bay record in db. And at this time, a
BayNotEmpty exception may raised if some of pods, services or rc
are related to this bay. In the meanwhile, the stack should be already
deleted, actually, the left bay record is unavailable.
This patch destroy the related resources when delete a bay.
Reviewed: https:/ /review. openstack. org/170764 /git.openstack. org/cgit/ openstack/ magnum/ commit/ ?id=dbb3769fa37 92bf804d5d31197 e3776eb4b7c9ff
Committed: https:/
Submitter: Jenkins
Branch: master
commit dbb3769fa3792bf 804d5d31197e377 6eb4b7c9ff
Author: lqslan <email address hidden>
Date: Mon Apr 6 10:33:59 2015 +0800
Destroy the related resources when delete a bay
Currently, when we delete a bay, we will delete the stack firstly,
then try to detroy the bay record in db. And at this time, a
BayNotEmpty exception may raised if some of pods, services or rc
are related to this bay. In the meanwhile, the stack should be already
deleted, actually, the left bay record is unavailable.
This patch destroy the related resources when delete a bay.
Change-Id: I56cd8813417bd4 a6f6c340deb8afd 88d5516f225
Closes-bug: #1440630