Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Created a user 2. launched few instances with that user 3. log in as admin and delete that user 4. Instances launched by user shows running Actual results: Expected results: Instances should be stopped and deleted . Additional info: rpm -qa|grep aeolus aeolus-conductor-0.8.0-4.el6.noarch aeolus-configure-2.5.0-2.el6.noarch aeolus-conductor-doc-0.8.0-4.el6.noarch aeolus-all-0.8.0-4.el6.noarch rubygem-aeolus-cli-0.3.0-3.el6.noarch rubygem-aeolus-image-0.3.0-2.el6.noarch aeolus-conductor-daemons-0.8.0-4.el6.noarch
Angus, Shveta has an interesting point here.. can you comment?
adding to ce-sprint
removing ce-sprint-next tracker
For 1.0, we should ask the admin to confirm that the user's instances will be terminated as part of deleting the user. Beyond that, we should develop UI around reassigning ownership of the user's assets.
Doesn't this overlap a good deal with https://bugzilla.redhat.com/show_bug.cgi?id=771599 in which we disallowed deletion of users if they had instances? Or are we saying we should reverse course?
Verified . User cannot be deleted now if it has running instance associated with it. If all instances launched by user are stopped , user can be deleted. rpm -qa|grep aeolus aeolus-conductor-0.8.0-8.el6.noarch aeolus-all-0.8.0-8.el6.noarch aeolus-conductor-daemons-0.8.0-8.el6.noarch rubygem-aeolus-image-0.3.0-3.el6.noarch aeolus-configure-2.5.0-5.el6.noarch rubygem-aeolus-cli-0.3.0-4.el6.noarch aeolus-conductor-doc-0.8.0-8.el6.noarch