Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. I have a pool quota of 7 and pool family quota of 6 instances 2. I am able to launch 7 instances irrespective quota limit of 6 in pool family. 3. Actual results: Expected results: Additional info: Screen shot attached rpm -qa|grep aeolus aeolus-conductor-daemons-0.3.0-0.el6.20110708135911gitdb1097c.noarch aeolus-configure-2.0.1-0.el6.20110708134115gitab1e6dc.noarch aeolus-all-0.3.0-0.el6.20110708135911gitdb1097c.noarch aeolus-conductor-0.3.0-0.el6.20110708135911gitdb1097c.noarch aeolus-conductor-doc-0.3.0-0.el6.20110708135911gitdb1097c.noarch rubygem-aeolus-cli-0.0.1-1.el6.20110708135911gitdb1097c.noarch
Created attachment 512201 [details] pool_family_quota_6
Created attachment 512204 [details] pool_quota
Fixed in fb129d7da19fea0b37d3ad01c6bb14afee6038c6
Errors * Some assemblies will not be launched: * frontend: Pool family quota reached Pool family quota is now enforced 1) Created provider account with quota of 5 2) Updated default pool family quota to 4 3) Updated default pool quota to 6 Was not able to launch more than 4 instance.
moving of the blocker
release pending...
release pending.. 2
perm close
closing out old bugs