[
https://issues.apache.org/jira/browse/CLOUDSTACK-8119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Likitha Shetty resolved CLOUDSTACK-8119.
----------------------------------------
Resolution: Fixed
During the addition of the 9th disks, while trying to decide the device number
on the controller key for the volume, CCP was picking the device number of the
previous volume. And that is why the disk addition failed with 'Invalid
configuration' in vCenter.
> [VMware] Attaching multiple volumes to a VM is failing.
> -------------------------------------------------------
>
> Key: CLOUDSTACK-8119
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8119
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
> Affects Versions: 4.5.0
> Reporter: Likitha Shetty
> Assignee: Likitha Shetty
> Priority: Critical
> Fix For: Future
>
>
> +Steps to reproduce+
> 1. Deploy a VM using default template.
> 2. Creat 13 volumes.
> 3. Attach 8 volumes to the VM.
> 4. Attach 9th volume to the VM, it will fail with following exception:
> {noformat}
> 2014-11-24 12:15:05,301 DEBUG [c.c.a.t.Request]
> (Work-Job-Executor-73:ctx-eea7360f job-612/job-613 ctx-455626cf) Seq
> 5-6870804181507113057: Executing: { Cmd , MgmtId: 6662467354709, via:
> 5(10.147.40.14), Ver: v1, Flags: 100011,
> [{"org.apache.cloudstack.storage.command.AttachCommand":{"disk":{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"7a3ae3ed-42dc-4b39-aa49-f247ccb5b20d","volumeType":"DATADISK","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"f159abf3-a686-3ff1-ad6a-24d59100bdb9","id":3,"poolType":"NetworkFilesystem","host":"10.147.28.7","path":"/export/home/manasa/primaryVMw2","port":2049,"url":"NetworkFilesystem://10.147.28.7/export/home/manasa/primaryVMw2/?ROLE=Primary&STOREUUID=f159abf3-a686-3ff1-ad6a-24d59100bdb9"}},"name":"vol10","size":5368709120,"path":"f43757595f63473eb2e49643f76b63f1","volumeId":89,"accountId":2,"format":"OVA","provisioningType":"THIN","id":89,"hypervisorType":"VMware"}},"diskSeq":9,"path":"f43757595f63473eb2e49643f76b63f1","type":"DATADISK","_details":{"managed":"false","storagePort":"2049","storageHost":"10.147.28.7","volumeSize":"5368709120"}},"vmName":"i-2-25-VM","inSeq":false,"diskController":"scsi","wait":0}}]
> }
> 2014-11-24 12:15:05,301 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-97:ctx-11cd0d9d) Seq 5-6870804181507113057: Executing request
> 2014-11-24 12:15:05,388 DEBUG [c.c.h.v.m.HostMO] (DirectAgent-97:ctx-11cd0d9d
> 10.147.40.14, job-612/job-613, cmd: AttachCommand) find VM i-2-25-VM on host
> 2014-11-24 12:15:05,388 INFO [c.c.h.v.m.HostMO] (DirectAgent-97:ctx-11cd0d9d
> 10.147.40.14, job-612/job-613, cmd: AttachCommand) VM i-2-25-VM not found in
> host cache
> 2014-11-24 12:15:05,388 DEBUG [c.c.h.v.m.HostMO] (DirectAgent-97:ctx-11cd0d9d
> 10.147.40.14, job-612/job-613, cmd: AttachCommand) load VM cache on host
> 2014-11-24 12:15:05,536 INFO [c.c.h.v.m.DatastoreMO]
> (DirectAgent-97:ctx-11cd0d9d 10.147.40.14, job-612/job-613, cmd:
> AttachCommand) Folder test2 exists on datastore
> 2014-11-24 12:15:05,541 INFO [c.c.h.v.m.DatastoreMO]
> (DirectAgent-97:ctx-11cd0d9d 10.147.40.14, job-612/job-613, cmd:
> AttachCommand) Search file f43757595f63473eb2e49643f76b63f1.vmdk on
> [f159abf3a6863ff1ad6a24d59100bdb9]
> 2014-11-24 12:15:05,562 INFO [c.c.h.v.m.DatastoreMO]
> (DirectAgent-97:ctx-11cd0d9d 10.147.40.14, job-612/job-613, cmd:
> AttachCommand) File [f159abf3a6863ff1ad6a24d59100bdb9]
> f43757595f63473eb2e49643f76b63f1.vmdk does not exist on datastore
> 2014-11-24 12:15:05,567 INFO [c.c.h.v.m.DatastoreMO]
> (DirectAgent-97:ctx-11cd0d9d 10.147.40.14, job-612/job-613, cmd:
> AttachCommand) Search file f43757595f63473eb2e49643f76b63f1.vmdk on
> [f159abf3a6863ff1ad6a24d59100bdb9] test2
> 2014-11-24 12:15:05,591 INFO [c.c.h.v.m.DatastoreMO]
> (DirectAgent-97:ctx-11cd0d9d 10.147.40.14, job-612/job-613, cmd:
> AttachCommand) File [f159abf3a6863ff1ad6a24d59100bdb9]
> test2/f43757595f63473eb2e49643f76b63f1.vmdk exists on datastore
> 2014-11-24 12:15:05,597 INFO [c.c.h.v.m.DatastoreMO]
> (DirectAgent-97:ctx-11cd0d9d 10.147.40.14, job-612/job-613, cmd:
> AttachCommand) Search file f43757595f63473eb2e49643f76b63f1-flat.vmdk on
> [f159abf3a6863ff1ad6a24d59100bdb9]
> 2014-11-24 12:15:05,622 INFO [c.c.h.v.m.DatastoreMO]
> (DirectAgent-97:ctx-11cd0d9d 10.147.40.14, job-612/job-613, cmd:
> AttachCommand) File [f159abf3a6863ff1ad6a24d59100bdb9]
> f43757595f63473eb2e49643f76b63f1-flat.vmdk does not exist on datastore
> 2014-11-24 12:15:05,630 INFO [c.c.h.v.m.DatastoreMO]
> (DirectAgent-97:ctx-11cd0d9d 10.147.40.14, job-612/job-613, cmd:
> AttachCommand) Search file f43757595f63473eb2e49643f76b63f1-delta.vmdk on
> [f159abf3a6863ff1ad6a24d59100bdb9]
> 2014-11-24 12:15:05,655 INFO [c.c.h.v.m.DatastoreMO]
> (DirectAgent-97:ctx-11cd0d9d 10.147.40.14, job-612/job-613, cmd:
> AttachCommand) File [f159abf3a6863ff1ad6a24d59100bdb9]
> f43757595f63473eb2e49643f76b63f1-delta.vmdk does not exist on datastore
> 2014-11-24 12:15:05,660 INFO [c.c.h.v.m.DatastoreMO]
> (DirectAgent-97:ctx-11cd0d9d 10.147.40.14, job-612/job-613, cmd:
> AttachCommand) Search file f43757595f63473eb2e49643f76b63f1.vmdk on
> [f159abf3a6863ff1ad6a24d59100bdb9]
> 2014-11-24 12:15:05,681 INFO [c.c.h.v.m.DatastoreMO]
> (DirectAgent-97:ctx-11cd0d9d 10.147.40.14, job-612/job-613, cmd:
> AttachCommand) File [f159abf3a6863ff1ad6a24d59100bdb9]
> f43757595f63473eb2e49643f76b63f1.vmdk does not exist on datastore
> 2014-11-24 12:15:05,733 INFO [c.c.h.v.u.VmwareContext]
> (DirectAgent-97:ctx-11cd0d9d 10.147.40.14, job-612/job-613, cmd:
> AttachCommand) Connected, conn:
> sun.net.www.protocol.https.DelegateHttpsURLConnection:https://10.147.60.18/folder/test2/f43757595f63473eb2e49643f76b63f1.vmdk?dcPath=manasa&dsName=f159abf3a6863ff1ad6a24d59100bdb9,
> retry: 0
> 2014-11-24 12:15:06,306 ERROR [c.c.s.r.VmwareStorageProcessor]
> (DirectAgent-97:ctx-11cd0d9d 10.147.40.14, job-612/job-613, cmd:
> AttachCommand) AttachVolumeCommand failed due to Exception:
> java.lang.RuntimeException
> Message: Invalid configuration for device '0'.
> java.lang.RuntimeException: Invalid configuration for device '0'.
> at
> com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:335)
> at
> com.cloud.hypervisor.vmware.mo.VirtualMachineMO.attachDisk(VirtualMachineMO.java:1131)
> at
> com.cloud.storage.resource.VmwareStorageProcessor.attachVolume(VmwareStorageProcessor.java:1353)
> at
> com.cloud.storage.resource.VmwareStorageProcessor.attachVolume(VmwareStorageProcessor.java:1281)
> at
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:139)
> at
> com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:59)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:469)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:304)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
> 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
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
> 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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> 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:722)
> 2014-11-24 12:15:06,307 DEBUG [c.c.a.m.DirectAgentAttache]
> (DirectAgent-97:ctx-11cd0d9d) Seq 5-6870804181507113057: Response Received:
> 2014-11-24 12:15:06,308 DEBUG [c.c.a.t.Request] (DirectAgent-97:ctx-11cd0d9d)
> Seq 5-6870804181507113057: Processing: { Ans: , MgmtId: 6662467354709, via:
> 5, Ver: v1, Flags: 10,
> [{"org.apache.cloudstack.storage.command.AttachAnswer":{"result":false,"details":"AttachVolumeCommand
> failed due to Exception: java.lang.RuntimeException\nMessage: Invalid
> configuration for device '0'.\n","wait":0}}] }
> 2014-11-24 12:15:06,308 DEBUG [c.c.a.t.Request]
> (Work-Job-Executor-73:ctx-eea7360f job-612/job-613 ctx-455626cf) Seq
> 5-6870804181507113057: Received: { Ans: , MgmtId: 6662467354709, via: 5,
> Ver: v1, Flags: 10, { AttachAnswer } }
> 2014-11-24 12:15:06,311 ERROR [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-73:ctx-eea7360f job-612/job-613 ctx-455626cf) Invocation
> exception, caused by: com.cloud.utils.exception.CloudRuntimeException: Failed
> to attach volume vol10 to VM test2; AttachVolumeCommand failed due to
> Exception: java.lang.RuntimeException
> Message: Invalid configuration for device '0'.
> 2014-11-24 12:15:06,311 INFO [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-73:ctx-eea7360f job-612/job-613 ctx-455626cf) Rethrow
> exception com.cloud.utils.exception.CloudRuntimeException: Failed to attach
> volume vol10 to VM test2; AttachVolumeCommand failed due to Exception:
> java.lang.RuntimeException
> Message: Invalid configuration for device '0'.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
