Hide Forgot
Description of problem: When a user deletes a deployable, the app should should ensure that all instances which the deployable contains are stopped before completing the deletion of the deployable itself. Version-Release number of selected component (if applicable): aeolus-conductor-0.3.0-0.fc14.20110711131044git5bc7abf.noarch How reproducible: Always Steps to Reproduce: 1. Launch a deployable which contains an instance 2. Navigate Pool details -> Deployable 3. Press "Delete" to delete the deployable, and confirm Actual results: Deployable is removed, but instances contained within it are not Expected results: Deployable is removed, and so are instances contained within it Additional info:
Sent a patch to the mailing list: https://fedorahosted.org/pipermail/aeolus-devel/2011-July/003291.html With that patch, we allow to delete deployment that has all of its instances either stopped or running. It will stop the running ones, delete the deployment and delete all associated instances.
Pushed into next: 742ec068d6c97bb9d69432eb441116365726eea3
Deleting a deployment stop and delete all associated instances and then delete the deployment itself. verified deleting deployments with instances stop and running. 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 [root@hp-dc5800-01 templates]#
release pending...
release pending.. 2
perm close
closing out old bugs