cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sateesh Chodapuneedi (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-3152) addVmwareDc API call fails if called more than once to add same VMware DC to same cloudstack zone.
Date Tue, 02 Jul 2013 13:00:20 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sateesh Chodapuneedi resolved CLOUDSTACK-3152.
----------------------------------------------

       Resolution: Fixed
    Fix Version/s: 4.2.0
    
> addVmwareDc API call fails if called more than once to add same VMware DC to same cloudstack
zone.
> --------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3152
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3152
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>    Affects Versions: 4.2.0
>            Reporter: Sateesh Chodapuneedi
>            Assignee: Sateesh Chodapuneedi
>             Fix For: 4.2.0
>
>
> This can be fixed by making addVmwareDC API return success if it is detected that VMware
DC and Cloudstack zone specified in paramters are already associated with each other.
> Add cluster page of zone wizard calls 2 APIs.
> 1) addVmwareDc
> 2) addCluster
> If call to addVmwareDc succeeds then UI proceeds to make a call to addCluster. If this
call fails then "Fix errors" takes user to addCluster page of zone wizard again.
> Again UI calls both the APIs. But this time addVmwareDc returns failure saying 
> "Something went wrong; please correct the following: Zone 1 is already associated with
a VMware datacenter.". If we goto "Fix errors" the process continues and user will be stuck
in infinite loop.

--
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

Mime
View raw message