[ https://issues.apache.org/jira/browse/CLOUDSTACK-4052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sudha Ponnaganti closed CLOUDSTACK-4052. ---------------------------------------- > vSphere VM state not updated within cloudstack > ---------------------------------------------- > > Key: CLOUDSTACK-4052 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4052 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, VMware > Affects Versions: 4.2.0 > Reporter: Ahmad Emneina > Assignee: Sateesh Chodapuneedi > Priority: Critical > Fix For: 4.2.0 > > > Issue 1: vSphere HA > Admin powered off a host within the cluster. VMware behaved as expected and > restarted the VMs on a different host within a minute or two. CloudStack also > detected the host going down within about a minute. > However, CloudStack never detects the VM as being 'started' again, when it > was booted by VMware HA. > Issue 2: vSphere VM Sync - State Not Updated > When a VM is shutdown from within the OS, CloudStack correctly detects that > it is down and changes the state to 'Stopped'. > However, If they turn this back on from within VMware, it never changes back > to 'Running'. > This means that in a HA scenario, the machine will never be manageable from > within CS until the user clicks the 'Start' button. However, this also > triggers CS to shut the machine down before it starts it again, which would > cause another outage for all machines that were recovered by HA. > The alert email from CS says that HA will be attempted within 1800 seconds > (30 minutes). We wouldnt want it to then try to start the VM itself 30 > minutes later and cause another outage. bad. bad CS! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira