You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Likitha Shetty (JIRA)" <ji...@apache.org> on 2013/12/09 12:41:08 UTC
[jira] [Created] (CLOUDSTACK-5416) [VMware] Not able to add seventh
disk to VM in an upgraded setup
Likitha Shetty created CLOUDSTACK-5416:
------------------------------------------
Summary: [VMware] Not able to add seventh disk to VM in an upgraded setup
Key: CLOUDSTACK-5416
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5416
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Storage Controller, VMware
Affects Versions: 4.2.1
Reporter: Likitha Shetty
Assignee: Likitha Shetty
Fix For: 4.3.0
Setup
-------
Upgraded to 4.2.1
Management-server log
------------------------------
2013-11-25 10:49:18,532 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-14:job-400 = [ 97adfe9c-225d-4699-a9b8-175ecac2e5c7 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
com.cloud.exception.InvalidParameterValueException: The specified VM already has the maximum number of data disks (6). Please specify another VM.
at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1793)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
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:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
Database entry
-------------------
Limit is still set to 6 for all versions of vSphere:
mysql> select
-> id,uuid,hypervisor_type,hypervisor_version,max_data_volumes_limit from
-> hypervisor_capabilities where hypervisor_type = 'VMware';
---------------------------------------------------------------
id uuid hypervisor_type hypervisor_version max_data_volumes_limit
---------------------------------------------------------------
10 10 VMware 4.0 6
11 11 VMware 4.1 6
12 12 VMware 5.0 6
13 13 VMware 5.1 6
9 9 VMware default 6
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)