If VMware host version is ESXi 4.1 and vCenter version is 5.0 or later, number of cores per socket of a VM running on ESXi 4.1 host would be undefined as it's not supported for versions prior to 5.0.
Hence expecting undefined/null value for that and handling it.
Signed-off-by: Sateesh Chodapuneedi <sateesh@apache.org>
When master router down, the back up router is entered into FAIL state
but it supposed to enter into master.
This issue is happening because the the enable_pubip.sh script triying to
ifdown and ifup the eth2 interface. Which is failed. So master.sh script got
failed. Fixed by doing ifdown force
Test whether valid storage pools are listed and at least one pool is
available for migration.
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
(cherry picked from commit a82f66e0fa8c9e20b0468aae82871c46a9f8b67e)
While upgrading to 4.2, the type of vswitch being used by each cluster is persisted to cluster_details table. This helps if user want to change the type of vswitch used in a zone or entire cloud later on but leave existing cluster continue to use old vswitches. Hence even after modifying the type of vswitch at cloud level (by modifying global configuration parameters) or modifying the type vswitch at zone level (by modifying the traffic label) would not disturb operation of existing clusters.
Signed-off-by: Sateesh Chodapuneedi <sateesh@apache.org>
XS Creating templates from volume - send the physical size in the copycommand which accordingly will populate template store ref and the usage_event tables with the right physical size
Signed off by : nitin mehta<nitin.mehta@citrix.com>
VM (id) moves from host (id) to host (id)
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
(cherry picked from commit da0bb630057550cb5707a39cddb58a86a24850dd)
Thereby failing the wget for the cloud-setup-guest-password script which
in turn fails the test.
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
(cherry picked from commit 8576b1ddc983d74caef77c3bac51103ab26cfc8c)
offerings do not need to be cleaned up
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
(cherry picked from commit b9c2471cfc5e051db4478783c6928f6e0c5a1f7a)
If all the VM's volumes are on zone wide primary storage pool then live migration of the VM would not involve storage migration. Hence MigrateVM API would be called against MigrateVMWithVolume. So far PrepareForMigrationCommand handled scenarios of VM moving across hosts within a cluster, but with zone wide primary storage in picture this command need to handle scenarios of VM moving across clusters. Try to find the VM in datacenter if not found within cluster.
Signed-off-by: Sateesh Chodapuneedi <sateesh@apache.org>
Introducing the option dhcp-client-update fails if the dnsmasq version is less than 2.6 (like in older templates).
Added a check for the version in cloud-early-config. will add dhcp-client-update option in the config file only
if the dnsmasq version is 2.6 and above.
Signed-off-by: Jayapal <jayapal@apache.org>
Simulator should revert back to CLOUD_DB after its operations on
SIMULATOR_DB or the cloudstack connections go to the simulator instead
of cloud.
Signed-off-by: Prasanna Santhanam <tsp@apache.org>
(cherry picked from commit 3d39716c8fed2b27edbd4475a7e0915b1200123c)
If you shut down the agent while VMs are running, the management
server assumes that the VMs are continuing to run. You can then
delete the host while it is in 'disconnected' state, and those VMs
will be unusable, forever in running state. They can't change state
because the host no longer exists. This patch checks for any VMs
that may have been tied to the removed host and resets their state
so that cloudstack can continue to manage them.
