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 CA3F710805 for ; Tue, 23 Dec 2014 08:43:13 +0000 (UTC) Received: (qmail 433 invoked by uid 500); 23 Dec 2014 08:43:13 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 399 invoked by uid 500); 23 Dec 2014 08:43:13 -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 390 invoked by uid 500); 23 Dec 2014 08:43:13 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 387 invoked by uid 99); 23 Dec 2014 08:43:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Dec 2014 08:43:13 +0000 Date: Tue, 23 Dec 2014 08:43:13 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-8112) Creating VM using an existing display name fails when vm.instancename.flag is set to true. 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-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256740#comment-14256740 ] ASF subversion and git services commented on CLOUDSTACK-8112: ------------------------------------------------------------- Commit 5f9e4fddf303f312a0b17abc0d837f28042caeda in cloudstack's branch refs/heads/master from [~likithas] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5f9e4fd ] CLOUDSTACK-8112. CS allows creation of VM's with the same Display name when vm.instancename.flag is set to true. During VM creation, if vm.instancename.flag is set to true and hypervisor type is VMware, check if VM with the same hostname already exists in the zone. > Creating VM using an existing display name fails when vm.instancename.flag is set to true. > ------------------------------------------------------------------------------------------ > > Key: CLOUDSTACK-8112 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8112 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Affects Versions: 4.5.0 > Reporter: Likitha Shetty > Assignee: Likitha Shetty > Fix For: Future > > > CS restricts 2 VMs from having the same name only if they are in the same network. But in case vm.instancename.flag is set to true, VM name in vCenter will be its VM's CS display name. And vCenter doesn't allow two VMs to have the same name under the same DC which results in the failure of VM start in CS and is not handled correctly. > CS should throw an error message to the user that a VM with the same name already exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)