You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sailaja Mada (JIRA)" <ji...@apache.org> on 2013/06/24 18:06:20 UTC
[jira] [Updated] (CLOUDSTACK-3162) [UI] UI does not allow to fix
errors with Cluster addition failure saying " Zone 1 is already associated
with a VMware datacenter"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sailaja Mada updated CLOUDSTACK-3162:
-------------------------------------
Fix Version/s: 4.2.0
> [UI] UI does not allow to fix errors with Cluster addition failure saying " Zone 1 is already associated with a VMware datacenter"
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3162
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3162
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: UI
> Affects Versions: 4.2.0
> Reporter: Sailaja Mada
> Priority: Critical
> Fix For: 4.2.0
>
>
> Steps:
> 1. Tried to configure Adv zone with Nexus 1000v enabled VMWARE cluster
> 2. It failed to VMWARE cluster with invalid nexus credentials issue
> 3. Later tried to add cluster again with correct credentials with Fix Errors option
> Observation:
> Cluster addition failed saying " Zone 1 is already associated with a VMware datacenter"
> I had to cancel the cluster add operation from zone config screen . Later i added cluster from clusters screen then it worked.
> Reasons:
> 1. AddVMWAREDC is called during cluster addition, when there is a failure in cluster addition with other reasons then we are not calling removeVMWAREDC to ensure proper cleanup.
> 2. Whenever we tried to add cluster using fix errors option , we are calling addVMWAREDc again. Which is not allowed as it is already added to vmware.
--
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