cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9458) Some VMs are being stopped when agent is reconnecting
Date Tue, 22 Nov 2016 05:23:58 GMT


ASF GitHub Bot commented on CLOUDSTACK-9458:

Github user koushik-das commented on the issue:
    @marcaurele Thats correct. In case of shared/remote storage the same disk is used to spawn
a VM on another host once the VM is successfully fenced. If the fencer has successfully fenced
off a VM, it is assumed that the original VM is correctly stopped. Now if you are saying that
the original VM continues to run then that means that the specific fencer has bugs and needs
fixing. Note that there are different types of fencer available in cloudstack based on hypervisor
    @abhinandanprateek In the scenario you mentioned vmsync won't be able to mark VM as stopped
as the ping command is no longer running as the host is in alert/down state.

> Some VMs are being stopped when agent is reconnecting
> -----------------------------------------------------
>                 Key: CLOUDSTACK-9458
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Marc-Aurèle Brothier
>            Assignee: Marc-Aurèle Brothier
> If you loose the communication between the management server and one of the agent for
a few minutes, even though HA mode is not active the HighAvailibilityManager kicks in and
start to schedule vm restart. Those tasks are being inserted as async job in the DB and if
the agent comes back online during the time the jobs are still in the async table, they are
pushed to the agent and shuts down the VMs. Then since HA is not active, the VM are not restarted.
> The expected behavior in my opinion is that the VM should not be restarted at all if
HA mode is not active on them, and let the agent update the VM state with the power report.
> The bug lies in {{HighAvailibilityManagerImpl.scheduleRestartForVmsOnHost(final HostVO
host, boolean investigate)}}, PR will follow.

This message was sent by Atlassian JIRA

View raw message