cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harikrishna Patnala (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CLOUDSTACK-1641) Vm Created with ISvolatile Service offering fails to start when it is restarted in the KVM Setup.
Date Fri, 15 Mar 2013 15:46:12 GMT

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

Harikrishna Patnala edited comment on CLOUDSTACK-1641 at 3/15/13 3:44 PM:
--------------------------------------------------------------------------

With the setup given in the description, I could not able to reproduce the issue, restore
vm works fine. 
I have checked the logs, the issue is related to multiple storage pools and NPE occured while
volume is getting migrated from one pool to another.
On vm start, Data disk is reallocating the storage pool even if the state is READY and NPE
is occurring when disk is trying to migrate from one pool to another. 
                
      was (Author: harikrishna.patnala):
    With the setup given in the description, I could not able to reproduce the issue, restore
vm works fine. 
But the issue is related to multiple storage pools and NPE occured while volume is getting
migrated from one pool to another.
On vm start, Data disk is reallocating the storage pool even if the state is READY and NPE
is occurring when disk is trying to migrate from one pool to another. 
                  
> Vm Created with ISvolatile Service offering fails to start when it is restarted in the
KVM Setup.
> -------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1641
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1641
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>         Environment: KVM  setup with master.
>            Reporter: Kiran Koneti
>            Assignee: Harikrishna Patnala
>            Priority: Blocker
>             Fix For: 4.2.0
>
>         Attachments: management-server.zip
>
>
> 1)Created a KVM Advanced Zone Setup.
> 2)Created a Service offereing with IS volatile true.
> 3)Created a VM using the service offering created above.
> 4)After Creating the VM restarted the VM using the UI.
> Then observed the following error message in the Managementserevr.log
> 2013-03-12 20:52:05,602 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-26:job-55)
Asking CiscoNexus1000vVSM to prepare for Nic[22-15-50ecc4b4-24be-42a2-ab93-520443349e9c-10.1.1.124]
> 2013-03-12 20:52:05,603 DEBUG [cloud.network.NetworkModelImpl] (Job-Executor-26:job-55)
Service SecurityGroup is not supported in the network id=204
> 2013-03-12 20:52:05,606 DEBUG [cloud.storage.VolumeManagerImpl] (Job-Executor-26:job-55)
Checking if we need to prepare 2 volumes for VM[User|IS5]
> 2013-03-12 20:52:05,608 DEBUG [cloud.storage.VolumeManagerImpl] (Job-Executor-26:job-55)
Mismatch in storage pool Pool[204|NetworkFilesystem] assigned by deploymentPlanner and the
one associated with volume Vol[33|vm=15|DATADISK]
> 2013-03-12 20:52:05,609 DEBUG [cloud.storage.VolumeManagerImpl] (Job-Executor-26:job-55)
Shared volume Vol[33|vm=15|DATADISK] will be migrated on storage pool Pool[204|NetworkFilesystem]
assigned by deploymentPlanner
> 2013-03-12 20:52:05,611 ERROR [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-26:job-55)
Failed to start instance VM[User|IS5]
> java.lang.NullPointerException
>         at com.cloud.storage.VolumeManagerImpl.prepare(VolumeManagerImpl.java:2288)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:616)
>         at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
>         at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
>         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
>         at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
>         at com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:40)
>         at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:616)
>         at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
>         at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
>         at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
>         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
>         at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
>         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
>         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
>         at $Proxy290.prepare(Unknown Source)
>         at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:750)
>         at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:468)
>         at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:461)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Attaching the management serever logs.

--
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

Mime
View raw message