sureshanaparti opened a new issue #4102:
URL: https://github.com/apache/cloudstack/issues/4102
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and master branch are affected too.
Always add information AFTER of these HTML comments, but no need to delete
the comments.
-->
Unable to attach more than 15 data disks to VMware VM. Currently, attaching
more than 15 data disks in VMware VM resulting in error "A specified parameter
was not correct: unitNumber" as CloudStack is picking up the same SCSI disk
controller to add the disk. CloudStack should pick the next available SCSI disk
controller and extend its support to attach more than 15 data disks.
##### ISSUE TYPE
<!-- Pick one below and delete the rest -->
* Improvement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
VM, Volume
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on master
branch.
-->
~~~
4.13.0
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
VMware hypervisor
##### SUMMARY
<!-- Explain the problem/feature briefly -->
VMware supports a maximum of 60 disks for a VM using the SCSI controller.
This support has to be extended in the CloudStack. Currently, attaching more
than 15 data disks in VMware VM resulting in error "A specified parameter was
not correct: unitNumber" as CloudStack is picking up the same SCSI disk
controller to add the disk. CloudStack should pick the next available SCSI disk
controller and extend its support to attach more than 15 data disks.
##### STEPS TO REPRODUCE
<!--
For bugs, show exactly how to reproduce the problem, using a minimal
test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
-->
1. Create a VM (in VMware hypervisor)
2. Attach upto 16 data disks to the VM
<!-- Paste example playbooks or commands between quotes below -->
~~~
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
Able to attach more than 15 data disks to VMware VM
~~~
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
Unable to attach more than 15 data disks to VMware VM. Attaching 16th disk
would fail with the error in the below log.
<!-- Paste verbatim command output between quotes below -->
~~~
2020-05-26 15:19:54,847 ERROR [c.c.s.r.VmwareStorageProcessor]
(DirectAgent-285:ctx-ad0fae96 10.2.3.133, job-541/job-542, cmd: AttachCommand)
(logid:d12a6740) Failed to attach volume: A specified parameter was not
correct: unitNumber
java.lang.RuntimeException: A specified parameter was not correct: unitNumber
at
com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:423)
at
com.cloud.hypervisor.vmware.mo.VirtualMachineMO.attachDisk(VirtualMachineMO.java:1287)
at
com.cloud.storage.resource.VmwareStorageProcessor.attachVolume(VmwareStorageProcessor.java:2012)
at
com.cloud.storage.resource.VmwareStorageProcessor.attachVolume(VmwareStorageProcessor.java:1922)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:149)
at
com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:62)
at
com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:536)
at
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315)
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:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
~~~
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
