Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Login to portal and delete default pool. 2. Create the default pool again through UI 3. Users , try to create a new User. message displays: Couldnt find pool with Id=1 Actual results: Expected results: Additional info:Screen shot attached. git show commit 70526a6f9b3b51e54c581f35410f255c3749a987 Author: Matt Wagner <mawagner> Date: Wed Jan 26 15:02:01 2011 -0500
Users will be prevented from deleting the default_pool. This is a temporary measure until the user creation process has the ability to associate users to specific pools.
Not fixed. User (admin) can delete default_pool . [root@usersys ~]# rpm -qa|grep aeolus aeolus-conductor-doc-0.0.3-0.fc14.20110305000715gita85c06f.x86_64 aeolus-configure-2.0.0-3.fc14.noarch aeolus-conductor-0.0.3-0.fc14.20110305000715gita85c06f.x86_64 aeolus-conductor-daemons-0.0.3-0.fc14.20110305000715gita85c06f.x86_64 7th March rpms.
Sorry I misunderstood the MODIFIED status. The change was submitted to the list for review. It has now been pushed to repo.
User is not able to delete default pool now , but the pop up message appears "Are you sure you want to delete this user?" It will be better if the pop up message is also bypassed (minor bug) . rpm -qa|grep aeolusaeolus-conductor-daemons-0.0.3-0.fc1420110309220719git7f7738b.x86_64 aeolus-configure-2.0.0-4.fc1420110309224940gite08f2c6.noarch aeolus-conductor-doc-0.0.3-0.fc1420110309220719git7f7738b.x86_64 aeolus-conductor-0.0.3-0.fc1420110309220719git7f7738b.x86_64
The message is changed to : "Are you sure you want to delete this pool?"
release pending...
perm close
closing out old bugs