[
https://issues.apache.org/jira/browse/CLOUDSTACK-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719401#comment-13719401
]
Hugo Trippaers commented on CLOUDSTACK-3781:
--------------------------------------------
This ticket appears to be related to a cloudplatform build, how does this build
relate to the open source version? Is this bug also present in CloudStack?
> Unable to resize disk on VmWare with Zone wide storage
> ------------------------------------------------------
>
> Key: CLOUDSTACK-3781
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3781
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Volumes
> Affects Versions: 4.2.0
> Environment: Cloudstack build : 257
> [http://repo-ccp.citrix.com/releases/ASF/rhel/6.3/4.2/CloudPlatform-4.2-257-rhel6.3.tar.gz]
> Hypervisor: Vmware Esxi 5.1
> Storage: NFS for both primary and secondary
> Reporter: Pavan Kumar Bandarupally
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: MS Log.rar
>
>
> When we create an instance on vmware and try to resize the data disk , it
> gives an error saying "Can't resize a volume that has never been attached,
> not sure which hypervisor type. Recreate volume to resize"
> An InvalidParameterValueException is being thrown as the hypervisor is
> getting selected as none. The problem is when the storage is added at zone
> level. The cluster_id is getting selected as NULL in this case. If the
> storage is added at cluster level, things work fine. Please see the db query
> below:
> mysql> SELECT c.hypervisor_type from volumes v, storage_pool s, cluster c
> where v.pool_id = s.id and s.cluster_id = c.id and v.id = 9;
> Empty set (0.00 sec)
> mysql> select * from storage_pool;
> +----+-------------+--------------------------------------+-------------------+------+----------------+--------+------------+---------------+----------------+--------------+-----------+----------------------------+---------------------+---------+-------------+--------+-----------------------+-------+------------+---------+---------------+
> | id | name | uuid | pool_type
> | port | data_center_id | pod_id | cluster_id | used_bytes |
> capacity_bytes | host_address | user_info | path |
> created | removed | update_time | status | storage_provider_name
> | scope | hypervisor | managed | capacity_iops |
> +----+-------------+--------------------------------------+-------------------+------+----------------+--------+------------+---------------+----------------+--------------+-----------+----------------------------+---------------------+---------+-------------+--------+-----------------------+-------+------------+---------+---------------+
> | 1 | TeamStorage | 0f658e18-7e6a-3442-9c36-de5c56926e26 | NetworkFilesystem
> | 2049 | 1 | NULL | NULL | 2001531498496 |
> 5902284800000 | 10.147.28.7 | NULL | /export/home/pavan/primary |
> 2013-07-24 15:53:00 | NULL | NULL | Up | DefaultPrimary
> | ZONE | VMware | 0 | NULL |
> +----+-------------+--------------------------------------+-------------------+------+----------------+--------+------------+---------------+----------------+--------------+-----------+----------------------------+---------------------+---------+-------------+--------+-----------------------+-------+------------+---------+---------------+
> 1 row in set (0.00 sec)
> mysql> select * from storage_pool\G
> *************************** 1. row ***************************
> id: 1
> name: TeamStorage
> uuid: 0f658e18-7e6a-3442-9c36-de5c56926e26
> pool_type: NetworkFilesystem
> port: 2049
> data_center_id: 1
> pod_id: NULL
> cluster_id: NULL
> used_bytes: 2001531498496
> capacity_bytes: 5902284800000
> host_address: 10.147.28.7
> user_info: NULL
> path: /export/home/pavan/primary
> created: 2013-07-24 15:53:00
> removed: NULL
> update_time: NULL
> status: Up
> storage_provider_name: DefaultPrimary
> scope: ZONE
> hypervisor: VMware
> managed: 0
> capacity_iops: NULL
> 1 row in set (0.00 sec)
> Repro Steps:
> ----------------
> Create an instance with a data disk attached.
> Go to the data disk and try to resize (increase) it.
> An error will be thrown.
> Note: Marking it as a blocker as we can't test Disk Re-size feature on VmWare
> because of this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
