You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Bharat Kumar (JIRA)" <ji...@apache.org> on 2013/12/24 11:27:50 UTC
[jira] [Commented] (CLOUDSTACK-5585) [Automation]Unable to stop VM
reported by HA Worker
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13856261#comment-13856261 ]
Bharat Kumar commented on CLOUDSTACK-5585:
------------------------------------------
The stopVM command is successful even if the HA worker fails.
> [Automation]Unable to stop VM reported by HA Worker
> ---------------------------------------------------
>
> Key: CLOUDSTACK-5585
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5585
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.3.0
> Environment: Xenserver
> advanced
> Reporter: Srikanteswararao Talluri
> Assignee: Bharat Kumar
> Priority: Critical
> Fix For: 4.3.0
>
>
> After this fix,
> i am hitting 'unable to stop VM' for a different reason. I will open another bug for this.
> 2013-12-18 13:17:50,490 WARN [c.c.v.VirtualMachineManagerImpl] (HA-Worker-0:ctx-8b1e82fb work-200) Unable to stop vm VM[User|QA-54b3a865-b499-4b65-9bbf-308b3b7e3209]
> 2013-12-18 13:17:50,504 DEBUG [c.c.c.CapacityManagerImpl] (HA-Worker-0:ctx-8b1e82fb work-200) VM state transitted from :Stopping to Running with event: OperationFailedvm's original host id: 2 new host id: 2 host id before state transition: 2
> 2013-12-18 13:17:50,504 ERROR [c.c.h.HighAvailabilityManagerImpl] (HA-Worker-0:ctx-8b1e82fb work-200) Terminating HAWork[200-Stop-612-Stopping-Scheduled]
> com.cloud.utils.exception.CloudRuntimeException: Unable to stop VM[User|QA-54b3a865-b499-4b65-9bbf-308b3b7e3209]
> at com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1398)
> at com.cloud.vm.VirtualMachineManagerImpl.orchestrateStop(VirtualMachineManagerImpl.java:1258)
> at com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1231)
> at com.cloud.ha.HighAvailabilityManagerImpl.stopVM(HighAvailabilityManagerImpl.java:651)
> at com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.runWithContext(HighAvailabilityManagerImpl.java:844)
> at com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.access$000(HighAvailabilityManagerImpl.java:797)
> at com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread$1.run(HighAvailabilityManagerImpl.java:809)
> at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
> at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
> at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
> at com.cloud.ha.HighAvailabilityManagerImpl$WorkerThread.run(HighAvailabilityManagerImpl.java:806)
> 2013-12-18 13:17:50,587 INFO [c.c.h.x.r.XenServer56Resource] (DirectAgent-225:ctx-f80fc44c) Catch com.xensource.xenapi.Types$VifInUse: failed to destory VLAN eth0 on host 06df9c52-24bf-49d0-a4c0-e635214bcf9f due to Network has active VIFs
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)