Uploaded image for project: 'CloudStack'
  1. CloudStack
  2. CLOUDSTACK-4304

ceph:nfsfail to attach a volume created from snapshot to same Instance

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 4.2.0
    • None
    • Volumes
    • Security Level: Public (Anyone can view this level - this is the default.)
    • None

    Description

      By default when we perform create volume form snapshot(which NFS based volume) it internally converting QCOW2 to RAW (RBD )format

      1.add nfs based ,RBD based primary storage
      2. add storage tags for primary storage and create compute offering for both storages
      like for
      nfs :normal
      RBD :RBD

      3. select the nfs based compute offering and deployed a VM
      4.Once it successful,select the root partition and perform snapshot
      5.once snapshot successful,create a volume from snapshot
      here it internally convering into RAW disk(qcow2 format to Raw format) even though snapshot volume is NFS bassed
      6.once it created,try to attche newly created data disk to same VM createdin step3

      Actual result:

      attach volume failed with error code 530 "Failed to attach volume: normalvolume to VM: normal; org.libvirt.LibvirtException: internal error unable to execute QEMU command 'device_add': Duplicate ID 'virtio-disk1' for device"

      http://10.147.59.110:8080/client/api?command=attachVolume&id=893e729f-aaed-438f-abc2-b5d662230078&virtualMachineId=361dc403-7e3f-4977-86ba-0589481f8259&response=json&sessionkey=3oaouwLLGveZlrYIn0zpMe4e394%3D&_=1376419838455

      { "queryasyncjobresultresponse" : {"accountid":"d4df5456-fe1d-11e2-9c5b-06a2f0000056","userid":"d4dff794-fe1d-11e2-9c5b-06a2f0000056","cmd":"org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd","jobstatus":2,"jobprocstatus":0,"jobresultcode":530,"jobresulttype":"object","jobresult":

      {"errorcode":530,"errortext":"Failed to attach volume: normalvolume to VM: normal; org.libvirt.LibvirtException: internal error unable to execute QEMU command 'device_add': Duplicate ID 'virtio-disk1' for device"}

      ,"created":"2013-08-13T20:18:47-0400","jobid":"cd3446fe-b082-4c90-8cd6-30036ccda59e"} }

      Agent log:

      [{"com.cloud.agent.api.PingAnswer":{"_command":{"hostType":"Routing","hostId":7,"contextMap":{},"wait":0},"result":true,"contextMap":{},"wait":0}}] }
      2013-08-14 00:20:34,385 TRACE [utils.nio.NioConnection] (Agent-Selector:null) Keys Processing: 1
      2013-08-14 00:20:34,386 TRACE [utils.nio.NioConnection] (Agent-Selector:null) Reading from: Socket[addr=/10.147.59.110,port=8250,localport=47605]
      2013-08-14 00:20:34,386 TRACE [utils.nio.Link] (Agent-Selector:null) Packet length is 758
      2013-08-14 00:20:34,386 TRACE [utils.nio.Link] (Agent-Selector:null) Done with packet: 737
      2013-08-14 00:20:34,386 TRACE [utils.nio.NioConnection] (Agent-Selector:null) Keys Done Processing.
      2013-08-14 00:20:34,387 DEBUG [cloud.agent.Agent] (agentRequest-Handler-5:null) Request:Seq 7-1066226815: { Cmd , MgmtId: 7296881000534, via: 7, Ver: v1, Flags: 100011, [{"org.apache.cloudstack.storage.command.AttachCommand":{"disk":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"893e729f-aaed-438f-abc2-b5d662230078","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"8e7c6fb5-c4d7-38f9-9cb1-d34d3bba4957","id":20,"poolType":"RBD","host":"10.147.41.3","path":"cloudstack","port":6789}},"name":"normalvolume","size":1599209472,"path":"2cb08bc5-3e14-4bd8-bc23-afdc9e47072d","volumeId":89,"accountId":2,"format":"QCOW2","id":89,"hypervisorType":"KVM"}},"diskSeq":1,"type":"DATADISK"},"vmName":"i-2-57-VM","_storageHost":"10.147.41.3","_storagePort":6789,"_managed":false,"contextMap":{},"wait":0}}] }
      2013-08-14 00:20:34,387 DEBUG [cloud.agent.Agent] (agentRequest-Handler-5:null) Processing command: org.apache.cloudstack.storage.command.AttachCommand
      2013-08-14 00:20:34,759 DEBUG [kvm.storage.KVMStorageProcessor] (agentRequest-Handler-5:null) Attaching device: <disk device='disk' type='network'>
      <driver name='qemu' type='raw' cache='none' />
      <source protocol='rbd' name='cloudstack/2cb08bc5-3e14-4bd8-bc23-afdc9e47072d'>
      <host name='10.147.41.3' port='6789'/>
      </source>
      <auth username='admin'>
      <secret type='ceph' uuid='8e7c6fb5-c4d7-38f9-9cb1-d34d3bba4957'/>
      </auth>
      <target dev='vdb' bus='virtio'/>
      </disk>

      2013-08-14 00:20:34,766 WARN [kvm.storage.KVMStorageProcessor] (agentRequest-Handler-5:null) Failed to attach device to i-2-57-VM: internal error unable to execute QEMU command 'device_add': Duplicate ID 'virtio-disk1' for device
      2013-08-14 00:20:34,767 DEBUG [kvm.storage.KVMStorageProcessor] (agentRequest-Handler-5:null) Failed to attach volume: 2cb08bc5-3e14-4bd8-bc23-afdc9e47072d, due to org.libvirt.LibvirtException: internal error unable to execute QEMU command 'device_add': Duplicate ID 'virtio-disk1' for device
      2013-08-14 00:20:34,767 DEBUG [cloud.agent.Agent] (agentRequest-Handler-5:null) Seq 7-1066226815: { Ans: , MgmtId: 7296881000534, via: 7, Ver: v1, Flags: 10, [{"org.apache.cloudstack.storage.command.AttachAnswer":{"result":false,"details":"org.libvirt.LibvirtException: internal error unable to execute QEMU command 'device_add': Duplicate ID 'virtio-disk1' for device","contextMap":{},"wait":0}}] }
      2013-08-14 00:20:34,767 TRACE [utils.nio.Link] (agentRequest-Handler-5:null) Sending packet of length 299
      2013-08-14 00:20:34,767 TRACE [utils.nio.NioConnection] (Agent-Selector:null) Keys Processing: 0
      2013-08-14 00:20:34,768 TRACE [utils.nio.NioConnection] (Agent-Selector:null) Keys Done Processing.
      2013-08-14 00:20:34,768 TRACE [utils.nio.NioConnection] (Agent-Selector:null) To

      Attachments

        Issue Links

          Activity

            People

              widodh Wido den Hollander
              sadhu sadhu suresh
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: