Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Sat, 17 May 2014 00:20:15 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12709904.1398207710220.373385.1400286015032@arcas>
In-Reply-To: <JIRA.12709904.1398207710220@arcas>
References: <JIRA.12709904.1398207710220@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-6476) Basic Zone with Multiple Pods
 Setup: DHCP server doesnt get deployed in the pod where the VM gets
 deployed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Commit 3448ab7f1c5c15949855788b029028ddac01327b in cloudstack's branch refs/heads/4.4-forward from [~prachidamle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3448ab7 ]

CLOUDSTACK-6476: Basic Zone with Multiple Pods Setup: DHCP server doesnt get deployed in the pod where the VM gets deployed

Changes:
PodId in which the router should get started was not being saved to the DB due to the VO's setter method not following the setXXX format. So when planner loaded the router from DB, it always got podId as null and that would allow planner to deploy the router in any pod. If the router happens to start in a different pod than the user VM, the Vm fails to start since the Dhcp service check fails.

Fixed the VO's setPodId method, that was causing the DB save operation fail.


> Basic Zone with Multiple Pods Setup: DHCP server doesnt get deployed in the pod where the VM gets deployed
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6476
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6476
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.4.0
>            Reporter: Chandan Purushothama
>            Assignee: Prachi Damle
>            Priority: Critical
>             Fix For: 4.4.0
>
>
> On deploying a new VM in a new Pod in a multiple Pod Basic Zone, the DHCP server that is supposed to the deployed in the new Pod gets deployed in another Pod. This results in VM Deployment Failure and disrupting the operations on other Pods.


--
This message was sent by Atlassian JIRA
(v6.2#6252)