Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a provider say for ec2 2. launch one instance in running state 3. Stop the instance 4. Try deleting the provider Account ssachdev was not deleted. There are instances associated with it. Actual results: Expected results: Additional info: rpm -qa|grep aeolus rubygem-aeolus-cli-0.0.1-1.el6.20110706142422git0ebf7d1.noarch aeolus-conductor-0.3.0-0.el6.20110706142422git0ebf7d1.noarch aeolus-configure-2.0.1-0.el6.20110706084705git542b456.noarch aeolus-conductor-doc-0.3.0-0.el6.20110706142422git0ebf7d1.noarch aeolus-all-0.3.0-0.el6.20110706142422git0ebf7d1.noarch aeolus-conductor-daemons-0.3.0-0.el6.20110706142422git0ebf7d1.noarch
I think we're referring to provider account here.
Fixed in commit ede71fb5187cea98135dca58bb24bbfb725375ea
Provider Account can be deleted if all instances are stopped. 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...
perm close