cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wido den Hollander (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-4657) ceph:fail to attach a volume to instance which is migrated from one primary to another primary.
Date Mon, 28 Apr 2014 19:56:16 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Wido den Hollander closed CLOUDSTACK-4657.
------------------------------------------

    Resolution: Fixed

I think this one is resolved as well.

I tried this on a 4.3 cluster (build from 4.3 branch) and it's working fine.

It was all related to a problem in the RADOS Java bindings and that all lead to 4665.

Should be resolved. Please re-open if it comes up again.

> ceph:fail to attach a volume to instance which is  migrated from one primary to another
primary.
> ------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4657
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4657
>             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
>            Reporter: sadhu suresh
>            Assignee: Wido den Hollander
>
> fail to attach a data  volume to instance after migrating instance from one primary to
another primary. due to problem specified in the issue #CLOUDSTACK-4652.
> 2.add RBD based primary storage
> 3.create compute offering and create a instance using this offering
> 4.stop the running VM which was created in step 3
> 5.perform migrate instance from one primary to another primary
> 6.create a data volume and try to attach  data volume to above instance
> actual result:
> attach volume is failing in this specific case.
> content of management log:
>     GET command=attachVolume&id=3d67606b-eeaf-474e-a7f4-95e24a4da7fd&virtualMachineId=42c31b97-d376-4e04-b6c3-08cecda7c13f&response=json&sessionkey=W%2F%2BBolWn%2BDoUEK1P92X71fVmknc%3D&_=1378979512588
>     2013-09-12 20:44:19,627 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-23
= [ 3158826e-9c85-4210-bc1a-d97ce9865a3d ]) Executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
for job-23 = [ 3158826e-9c85-4210-bc1a-d97ce9865a3d ]
>     2013-09-12 20:44:19,956 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-23
= [ 3158826e-9c85-4210-bc1a-d97ce9865a3d ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
>     com.cloud.utils.exception.CloudRuntimeException: The VM VM33 has more than one ROOT
volume and is in an invalid state.
>     at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1815)
>     at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>     at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
>     at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
>     at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
>     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>     at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>     at java.lang.Thread.run(Thread.java:679)
>     2013-09-12 20:44:19,980 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-23
= [ 3158826e-9c85-4210-bc1a-d97ce9865a3d ]) Complete async job-23 = [ 3158826e-9c85-4210-bc1a-d97ce9865a3d
], jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: The VM VM33 has more
than one ROOT volume and is in an invalid state.
>     2013-09-12 20:44:22,270 DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-3:null)
SeqA 2-1802: Processing Seq 2-1802: { Cmd , MgmtId: -1, via: 2, Ver: v1, Flags: 11, [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"
{\n \"connections\": []\n}
>     ","wait":0}}] }
>     2013-09-12 20:44:22,279 DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-3:null)
SeqA 2-1802: Sending Seq 2-1802: { Ans: , MgmtId: 7175246184473, via: 2, Ver: v1, Flags: 100010,
[{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
>     2013-09-12 20:44:22,497 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null) ===START===
10.252.192.100 – GET command=queryAsyncJobResult&jobId=3158826e-9c85-4210-bc1a-d97ce9865a3d&response=json&sessionkey=W%2F%2BBolWn%2BDoUEK1P92X71fVmknc%3D&_=1378979516168
>     2013-09-12 20:44:22,508 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-14:null)
Async job-23 = [ 3158826e-9c85-4210-bc1a-d97ce9865a3d ] completed
>     2013-09-12 20:44:22,514 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null) ===END===
10.252.192.100 – GET command=queryAsyncJobResult&jobId=3158826e-9c85-4210-bc1a-d97ce9865a3d&response=json&sessionkey=W%2F%2BBolWn%2BDoUEK1P92X71fVmknc%3D&_=1378979516168



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

Mime
View raw message