Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 11 Jul 2014 13:01:07 +0000 (UTC)
From: "Daan Hoogland (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12693387.1391616801868.23343.1405083667657@arcas>
In-Reply-To: <JIRA.12693387.1391616801868@arcas>
References: <JIRA.12693387.1391616801868@arcas>
Subject: [jira] [Comment Edited] (CLOUDSTACK-6036)  CloudStack stops the
 machine for no reason
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-6036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058733#comment-14058733 ] 

Daan Hoogland edited comment on CLOUDSTACK-6036 at 7/11/14 1:00 PM:
--------------------------------------------------------------------

Damodar, can you comment on the status of this issue? It gets a minus one to the 4.4.0 release


was (Author: dahn):
Damodar, can you comment on the status of this issue?

>  CloudStack stops the machine for no reason
> -------------------------------------------
>
>                 Key: CLOUDSTACK-6036
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6036
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.1
>         Environment: ACS 4.2.1 after upgrade from 3.0.2
> ACS 4.2.1 clean install
> XCP 1.1
>            Reporter: Tomasz Zieba
>            Assignee: Damodar Reddy T
>            Priority: Critical
>             Fix For: 4.4.0
>
>         Attachments: management-server.log.2014-02-19.gz, management-server.log.2014-02-20.gz, management-server.log.2014-02-24.txt
>
>
> After the upgrade from version 3.0.2 to 4.2.1 appeared very strange error associated with self-stopping machine after changing the offering. 
> Steps to reproduce: 
> 1. Running instance of the machine 
> 2. Stop with the operating system 
> 3. Change offering of machine
> 4. Start the machine 
> 5. Waiting for 10 minutes 
> 6. CloudStack stops the machine for no reason
> 7. Restart the machine 
> In the logs you can find information:
> 2014-02-05 06:27:00,974 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-316:null) 11. The VM i-41-824-VM is in Running state
> 2014-02-05 06:27:00,974 DEBUG [agent.transport.Request] (DirectAgent-316:null) Seq 50-1756626952: Processing:  { Ans: , MgmtId: 160544475005497, via: 50, Ver: v1, Flags: 10, [{"com.cloud.agent.api.ClusterSyncAnswer":{"_clusterId":2,"_newStates":{"i-41-824-VM":{"t":"f32a4fee-b64e-4868-9c52-2a27e32d4c0e","u":"Running","v":"viridian:true;acpi:true;apic:true;pae:true;nx:false;timeoffset:0;cores-per-socket:4"}},"_isExecuted":false,"result":true,"wait":0}}] }
> 2014-02-05 06:27:00,981 DEBUG [cloud.vm.VirtualMachineManagerImpl] (DirectAgent-316:null) VM i-41-824-VM: cs state = Running and realState = Running
> 2014-02-05 06:27:00,981 DEBUG [cloud.vm.VirtualMachineManagerImpl] (DirectAgent-316:null) VM i-41-824-VM: cs state = Running and realState = Running
> 2014-02-05 06:36:01,240 DEBUG [agent.transport.Request] (HA-Worker-1:work-1511) Seq 51-1374970375: Sending  { Cmd , MgmtId: 160544475005497, via: 51, Ver: v1, Flags: 100111, [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":true,"vmName":"i-41-824-VM","wait":0}}] }
> 2014-02-05 06:36:01,240 DEBUG [agent.transport.Request] (HA-Worker-1:work-1511) Seq 51-1374970375: Executing:  { Cmd , MgmtId: 160544475005497, via: 51, Ver: v1, Flags: 100111, [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":true,"vmName":"i-41-824-VM","wait":0}}] }
> 2014-02-05 06:36:01,383 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-150:null) 9. The VM i-41-824-VM is in Stopping state
> 2014-02-05 06:36:27,625 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-150:null) 10. The VM i-41-824-VM is in Stopped state
> You will notice that the stop of the machine corresponds to the component HA-Worker. 
> Such operation after the upgrade is complicating work of users.


--
This message was sent by Atlassian JIRA
(v6.2#6252)