prachi 0eea1cb733 Bug 11404 - VM was in Running state, had null for a pod_id, basically didnt allow creation of subsequent vm's ... Reviewed-by: Alex Changes: - When management server starts, it goes through all the pending work items from op_it_work table and schedules HA work for each. It used to mark each item as done. Instead we should keep the item as pending and let it get marked as Done after the HA work is done. - Changes in VirtualMachineMgr::advanceStop() : a) if we find a VM with null hostId, we stop the VM only if it is forced stopped. b) if VM state transition to Stopping fails,for state Starting and Migrating we try to find the pending work item and then do cleanup the VM. In case state is Stopping we can cleanup directly. c) We proceed releasing all resources only if state transitioned to 'Stopping'. - Changes in HA: a) Depend on VirtualMachineMgr::advanceStop() in case host is not found to do VM cleanup - When Vm state between mgmt server and agent syncs from starting -> running, mark any pending work item as done. Conflicts: server/src/com/cloud/vm/VirtualMachineManagerImpl.java		2011-09-15 19:06:19 -07:00
..
manager	Bug 11404 - VM was in Running state, had null for a pod_id, basically didnt allow creation of subsequent vm's	2011-09-15 19:06:19 -07:00
AgentManager.java	1. added timeout in Command Class, then each command can configure itself timeout, if timeout is not configed, use the default timeout , which is 30 minute	2011-09-07 19:17:54 -07:00
VmmAgentShell.java	Full opensource	2011-08-23 19:52:19 -07:00