cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fang Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2725) [Automation] Re-attaching volume on VM failing in KVM
Date Sat, 13 Jul 2013 00:39:48 GMT

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

Fang Wang commented on CLOUDSTACK-2725:
---------------------------------------

The bug was reproduced by the smoke test and I checked the libvirt log, libvirt reported an
error: 

So 
2013-07-12 05:53:10.458+0000: 5739: error : qemuMonitorJSONCheckError:355 : internal error
unable to execute QEMU command '__com.redhat_drive_add': Duplicate ID 'drive-virtio-disk1'
for drive
2013-07-12 05:53:16.001+0000: 5743: error : qemuMonitorJSONCheckError:355 : internal error
unable to execute QEMU command '__com.redhat_drive_add': Duplicate ID 'drive-virtio-disk1'
for drive
2013-07-12 05:53:16.862+0000: 5738: error : qemuProcessFindDomainDiskByAlias:406 : internal
error no disk found with alias

it seems after the detach, and then attach, the same device id is used, but the driver did
not think the original one is detached yet.

It is a libvirt issue. 
                
> [Automation] Re-attaching volume on VM failing in KVM
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-2725
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2725
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Volumes
>    Affects Versions: 4.2.0
>         Environment: Automation environment KVM 
> Found in master also (8d1189c2ae87216bc1c4a1443f75e9a8629abdc2)
>            Reporter: Rayees Namathponnan
>            Assignee: Fang Wang
>            Priority: Blocker
>             Fix For: 4.2.0
>
>         Attachments: CLOUDSTACK-2725.rar
>
>
> Below two test case failing from BVT 
> integration.smoke.test_volumes.TestVolumes.test_08_resize_volume 
> integration.smoke.test_volumes.TestVolumes.test_09_delete_detached_volume 
> Steps to reproduce 
> Step 1 : Create an account, service offering, create volume, create VM
> Step 2 : Attach volume to VM , 
> Step 3 : Detach volume
> Step 4 : Attach volume to VM  again 
> Actual result 
> Attachment failed with below error
> 2013-05-28 13:45:39,101 DEBUG [agent.transport.Request] (Job-Executor-98:job-1246) Seq
5-258539658: Rec
> eived:  { Ans: , MgmtId: 29066118877352, via: 5, Ver: v1, Flags: 10, { AttachAnswer }
}
> 2013-05-28 13:45:39,106 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-98:job-1246)
Unexpected e
> xception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume: TestDiskServ
to VM: ce79edb6-
> a306-4ac4-95e4-6202800f691e; org.libvirt.LibvirtException: internal error unable to execute
QEMU comman
> d '__com.redhat_drive_add': Duplicate ID 'drive-virtio-disk1' for drive
>         at com.cloud.storage.VolumeManagerImpl.sendAttachVolumeCommand(VolumeManagerImpl.java:1583)
>         at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1788)
>         at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercep
> t(ComponentInstantiationPostProcessor.java:125)
>         at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:1
> 22)
>         at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
>         at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
>         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:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:679)
> 2013-05-28 13:45:39,107 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-98:job-1246)
Complete asy
> nc job-1246, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed
to attach volume
> : TestDiskServ to VM: ce79edb6-a306-4ac4-95e4-6202800f691e; org.libvirt.LibvirtException:
internal erro

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