[
https://issues.apache.org/jira/browse/CLOUDSTACK-3800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818463#comment-13818463
]
Paul Angus commented on CLOUDSTACK-3800:
----------------------------------------
Surely the tag should be at the cluster level not the datacenter level as well.
I know of a number of clients how have multiple environments controlled by
multiple CloudStack instances in the same datacenter.
> Provide input parameter "force" to addVmwareDc API
> --------------------------------------------------
>
> Key: CLOUDSTACK-3800
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3800
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Reporter: Sateesh Chodapuneedi
> Assignee: Sateesh Chodapuneedi
>
> Cloudstack sets custom field (over specific VMware DC) named 'cloud.zone' to
> true when a VMware DC is added to cloudstack, to indicate that this VMware DC
> is being used by this cloudstack deployment. But if user wants to re-deploy
> new cloudstack instance after improper cleanup of earlier setup (without
> disassociating/removing VMware DC from zone using UI or removeVmwareDc API)
> then while re-deploying user will see following error while adding Vmware DC
> to zone.
> ""Failed to add VMware DC to zone due to : This DC is being managed by other
> CloudStack deployment. Cannot add this DC to zone."
> If user would like to force the addition of VMware DC to zone knowing that he
> can use force parameter setting to true.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
