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

ASF GitHub Bot commented on CLOUDSTACK-9794:
--------------------------------------------

Github user sureshanaparti commented on the issue:

    https://github.com/apache/cloudstack/pull/1953
  
    Changes in the PR #2019.
    
    Maximum data volumes supported field, in the _hypervisor_capabilities_ 
table, should be the attachable data volumes to the VM. This excludes the ROOT 
disk and CD-ROM. So, the hypervisor has to support max devices = maximum data 
volumes supported + 2 (ROOT and CD-ROM).
    
    0(zero) index is considered in `getDeviceId()` for ROOT disk as the ROOT 
disk attach cmd uses this method. This has to be refactored.


> Unable to attach more than 14 devices to a VM
> ---------------------------------------------
>
>                 Key: CLOUDSTACK-9794
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9794
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Volumes
>            Reporter: Suresh Kumar Anaparti
>            Assignee: Suresh Kumar Anaparti
>             Fix For: 4.10.0.0
>
>
> A limit of 13 disks is set in hypervisor_capabilities for VMware hypervisor. 
> Changed this limit to a higher value in the DB directly for the VMware and 
> tried attaching more than 14 disks. This was failing with the below exception:
> {noformat}
> 2016-08-12 18:42:53,694 ERROR [c.c.a.ApiAsyncJobDispatcher] 
> (API-Job-Executor-40:ctx-56068c6b job-1015) (logid:b22938fd) Unexpected 
> exception while executing 
> org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin
> java.util.NoSuchElementException
>       at java.util.ArrayList$Itr.next(ArrayList.java:794)
>       at 
> com.cloud.storage.VolumeApiServiceImpl.getDeviceId(VolumeApiServiceImpl.java:2439)
>       at 
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1308)
>       at 
> com.cloud.storage.VolumeApiServiceImpl.attachVolumeToVM(VolumeApiServiceImpl.java:1173)
>       at sun.reflect.GeneratedMethodAccessor248.invoke(Unknown Source)
>       at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>       at java.lang.reflect.Method.invoke(Method.java:601)
>       at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
>       at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
>       at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
>       at 
> org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:106)
> {noformat}
> There was a hardcoded limit of 15 on the number of devices for a VM.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to