Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Date: Tue, 19 Feb 2013 23:19:13 +0000 (UTC)
From: "Prachi Damle (JIRA)" <jira@apache.org>
To: cloudstack-dev@incubator.apache.org
Message-ID: <JIRA.12633095.1361315170299.307441.1361315953227@arcas>
In-Reply-To: <JIRA.12633095.1361315170299@arcas>
References: <JIRA.12633095.1361315170299@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-1330) ec2-run-instances - When -n
 option is used to deploy multiple Vms API returns error even though few of
 the Vms have been deployed successfully.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581736#comment-13581736 ] 

Prachi Damle commented on CLOUDSTACK-1330:
------------------------------------------

Fixed.

Changes:
- Instead of throwing out error, return the response containing the info about the instances that were launched.


In master.
Commit hash:	8296d41b5bd340e98d9e48ced884aab56f61e0ac

4.1:
Commit hash:	f900d0bc71e8edded33f4e18f22153bfd258fbcd
                
> ec2-run-instances - When -n option is used to deploy multiple Vms API returns error even though few of the Vms have been deployed successfully.
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1330
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1330
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: AWSAPI
>    Affects Versions: pre-4.0.0, 4.0.0
>            Reporter: Prachi Damle
>            Assignee: Prachi Damle
>             Fix For: 4.1.0
>
>
> ec2-run-instances - When -n option is used to deploy multiple Vms when there is not enough capcity to deploy all the Vms, api returns error even though few of the Vms have been deployed successfully.
> Steps to reproduce the problem:
> Set up:
> Basic Zone
> Guest Range -> Had about 16 ipaddresses out of which 8 of them were alreday taken up for system Vms and user Vms.
> Try to deploy 20 more vms using the following command:
> [root@Host50-9 bin]# ./ec2-run-instances aebeba5c-661d-4b0d-82c2-dfd4f253dcd6 -n 5-20 --connection-timeout 600 --request-timeout 600
> Server.InternalError: 533 Unable to create a deployment for VM[User|b96f45f6-20e2-4a5a-9bf2-63296161fc30]
> API returns error.
> Expected Result:
> We should be returning the 8 user Vms that were actually deployed successfully using this api call.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira