Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C610F107BC for ; Sun, 10 Nov 2013 15:32:24 +0000 (UTC) Received: (qmail 12778 invoked by uid 500); 10 Nov 2013 15:32:22 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 12763 invoked by uid 500); 10 Nov 2013 15:32:18 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 12756 invoked by uid 500); 10 Nov 2013 15:32:18 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 12752 invoked by uid 99); 10 Nov 2013 15:32:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Nov 2013 15:32:17 +0000 Date: Sun, 10 Nov 2013 15:32:17 +0000 (UTC) From: "Paul Angus (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-3800) Provide input parameter "force" to addVmwareDc API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)