[
https://issues.apache.org/jira/browse/CLOUDSTACK-6476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020538#comment-14020538
]
ASF subversion and git services commented on CLOUDSTACK-6476:
-------------------------------------------------------------
Commit 3b3f4577b0f4a86cc6f26a9999a14621d3aba37a in cloudstack's branch
refs/heads/master from [~prachidamle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3b3f457 ]
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)
