cloudstack/engine
Prachi Damle 3b3f4577b0 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.
2014-06-06 16:15:31 -07:00
..
api CLOUDSTACK-6599: 2014-05-30 10:48:42 -07:00
components-api Fixed CLOUDSTACK-6756: usage id is not being returned for an ip in deleted ip range 2014-05-27 10:41:40 +05:30
network findbugs: exclude known spiffy hacks a.k.a. false positives 2014-03-28 14:28:10 +01:00
orchestration CLOUDSTACK-6476: Basic Zone with Multiple Pods Setup: DHCP server doesnt get deployed in the pod where the VM gets deployed 2014-06-06 16:15:31 -07:00
schema CLOUDSTACK-6476: Basic Zone with Multiple Pods Setup: DHCP server doesnt get deployed in the pod where the VM gets deployed 2014-06-06 16:15:31 -07:00
service findbugs: exclude known spiffy hacks a.k.a. false positives 2014-03-28 14:28:10 +01:00
storage CLOUDSTACK-6599: 2014-05-30 10:48:42 -07:00
pom.xml Update master to 4.5.0-SNAPSHOT 2014-03-14 14:55:26 +01:00