Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 17 Aug 2016 15:40:20 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12997478.1471327169000.332039.1471448420491@Atlassian.JIRA>
In-Reply-To: <JIRA.12997478.1471327169000@Atlassian.JIRA>
References: <JIRA.12997478.1471327169000@Atlassian.JIRA> <JIRA.12997478.1471327169861@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-9458) Some VMs are being stopped
 when agent is reconnecting
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 17 Aug 2016 15:40:22 -0000


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9458?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D15424736#comment-15424736 ]=20

ASF GitHub Bot commented on CLOUDSTACK-9458:
--------------------------------------------

Github user jburwell commented on the issue:

    https://github.com/apache/cloudstack/pull/1640
 =20
    Are there Marvin test cases to verify this behavior?


> Some VMs are being stopped when agent is reconnecting
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-9458
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-945=
8
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>            Reporter: Marc-Aur=C3=A8le Brothier
>            Assignee: Marc-Aur=C3=A8le Brothier
>
> If you loose the communication between the management server and one of t=
he agent for a few minutes, even though HA mode is not active the HighAvail=
ibilityManager kicks in and start to schedule vm restart. Those tasks are b=
eing inserted as async job in the DB and if the agent comes back online dur=
ing 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 r=
estarted.
> The expected behavior in my opinion is that the VM should not be restarte=
d 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
(v6.3.4#6332)