Koushik Das 7dca2a5702 Fix CS-15603. When a VM is force deleted and the host is not available then CS simply marks the state in db as "Destroyed/Expunging". The VM is still running on the host and once it becomes available again there is a discrepancy in state of the VM. In this scenario the VM is removed from the host when the next full cluster sync happens. ... Reviewed-by: Abhi		2012-07-19 15:51:11 +05:30
..
conf	Removed bad word from log4j config files.	2011-02-08 13:55:40 -08:00
scripts	Source code committed	2010-08-11 09:13:29 -07:00
src/com/cloud	Fix CS-15603. When a VM is force deleted and the host is not available then CS simply marks the state in db as "Destroyed/Expunging". The VM is still running on the host and once it becomes available again there is a discrepancy in state of the VM. In this scenario the VM is removed from the host when the next full cluster sync happens.	2012-07-19 15:51:11 +05:30
test	bug 12105: don't generate corresponding firewall rule for the pf/staticNat/lb rule in revoke state	2011-11-21 16:25:00 -08:00
.classpath	bug 11230, 11229: merge fix from 2.2.10 branch, fix Eclipse project settings for premium-move	2011-08-24 15:16:59 -07:00
.project	Fix corrupted eclipse project settings, schema fixes and updated template download url	2010-09-29 18:41:54 -07:00