Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: I enforced cloud quota such a way that only 1 instance can be launched out of 2 instances from muti-instance deployable. so while launching the deployment, 1 instances should get launched and for the second one it should display "cloud quota reached". But this does not happen.Both the instances are getting launched.it seems cloud quota is not checked while launching multi instance deployment. see attached screenshot. Note: cloud quota is checked for single instance deployment and displays message " cloud quota reached" which is correct. Expected results: Cloud quota should be enforced for multi-instance deployment. Additional info: rpm -qa | grep aeolus aeolus-conductor-0.8.0-17.el6.noarch rubygem-aeolus-cli-0.3.0-7.el6.noarch aeolus-configure-2.5.0-11.el6.noarch aeolus-conductor-daemons-0.8.0-17.el6.noarch aeolus-all-0.8.0-17.el6.noarch aeolus-conductor-doc-0.8.0-17.el6.noarch rubygem-aeolus-image-0.3.0-7.el6.noarch
Created attachment 558760 [details] cloud quota
The solution for this is to check the quota before launch, and if there isn't sufficient quota remaining to launch all of the instances defined in the deployable, not to launch the deployable at all. Partially launching the deployable, by starting as many instances as the quota permits, would be likely to leave the user with a non-functional deployment.
Patch created; it prevents multi-instance deployables from launching at all if doing so would go over the pool/pool family quota: https://fedorahosted.org/pipermail/aeolus-devel/2012-February/008593.html
Pushed to 1.0-staging: commit 78cbf85d6de7bdfe5c26a417b580cdd9c829efb8 BZ 786344 added pre-launch validation for multi-instance deployments
Created attachment 565301 [details] quota for multi assembly deployment Before launching quota is checked for multi assembly deployment rpm -qa|grep aeolus aeolus-conductor-0.8.0-35.el6.noarch rubygem-aeolus-cli-0.3.0-10.el6.noarch aeolus-conductor-doc-0.8.0-35.el6.noarch rubygem-aeolus-image-0.3.0-9.el6.noarch aeolus-all-0.8.0-35.el6.noarch aeolus-conductor-daemons-0.8.0-35.el6.noarch aeolus-configure-2.5.0-15.el6.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2012-0583.html