Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 20 Dec 2013 21:40:10 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12685892.1387574111771.74930.1387575610406@arcas>
In-Reply-To: <JIRA.12685892.1387574111771@arcas>
References: <JIRA.12685892.1387574111771@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-5597) attachVolume shouldn't create
 the volume on the primary storage if the vm's root volume is not created
 yet
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-5597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13854581#comment-13854581 ] 

ASF subversion and git services commented on CLOUDSTACK-5597:
-------------------------------------------------------------

Commit 1832cf6660085ee253a4daf6eabe0b15843ae1c9 in branch refs/heads/master from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1832cf6 ]

CLOUDSTACK-5597: don't perform data disk allocation on the primary storage when attachVolume calls is made for the vm which ROOT disk hasn't been created yet.


> attachVolume shouldn't create the volume on the primary storage if the vm's root volume is not created yet
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5597
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5597
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>            Reporter: Alena Prokharchyk
>            Assignee: Alena Prokharchyk
>             Fix For: 4.4.0
>
>
> In cloudStack you can deploy a vm w/o actually starting it on the backend (startVm=false parameter should be passed to deployVm call to trigger this behavior). When vm is not started during the original deployment, its ROOT volume is not created either. It stays in Allocated state in the DB.
> Bug: when try to attach data disk to such a vm, current CS code creates it on the primary storage.
> The fix should be: when check to see if the volume needs to be created on the primary storage, validate the Vm's Root volume state. And if its Allocated, don't create it.


--
This message was sent by Atlassian JIRA
(v6.1.4#6159)