Hide Forgot
Description of problem: Right now its possible to destroy pool with running deployments. The pool should be removable only with deployments with instances in stopped or create_failed state. Version-Release number of selected component (if applicable): How reproducible: Create a pool "testpool", launch a new deployment in that "testpool", delete "testpool". Go to Overview - filter view, select deployments tab, receive error.
fixed in commit 89a6b60375a3f1c37472ac900dbf479076418c6f
Pool cannot be deleted =with running deployments. Message is displayed "Pool testpool was not deleted. There are instances associated with it." verified on: [root@hp-dc5800-01 templates]# rpm -qa | grep aeolus aeolus-conductor-doc-0.3.0-0.el6.20110721214453git381316a.noarch aeolus-conductor-daemons-0.3.0-0.el6.20110721214453git381316a.noarch rubygem-aeolus-image-0.0.1-1.el6.20110721174118git6f9d8d4.noarch aeolus-all-0.3.0-0.el6.20110721214453git381316a.noarch aeolus-conductor-0.3.0-0.el6.20110721214453git381316a.noarch aeolus-configure-2.0.1-1.el6.20110721154028git42b1e20.noarch
moving verified bugs off the tracker
release pending...
closing out old bugs
perm close