[
https://issues.apache.org/jira/browse/CLOUDSTACK-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726395#comment-13726395
]
Rajesh Battala commented on CLOUDSTACK-3781:
--------------------------------------------
This issue will apply to all the Hypervisors where ZWPS is supported.
root cause the sql query to find the out hypervisor where the volume is
present.
this is the query getting executed to find the hypervisor type for the volume.
mysql> SELECT s.hypervisor, 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 = 13;
when the volume is in ZONE scope, then this query will return empty results as
the the storage pool won't have cluster id if the pool is of zone scope. (
because s.cluster_id will be null and there is no NULL cluster id in cluster
table)
This is working well in case of the pool scope is Cluster. as the pool will
store the cluster id if the scope is CLUSTER, as s.cluster_id is present and
it matches to c.id we are able to find the hypervisor type.
We need to fix the sql query to fetch the hypervisor type depending on the
storage pool.
> Unable to resize disk 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: Management Server: CentOS6.2 with latest 4.2 cloudstack
> build
> Hypervisor: Vmware Esxi 5.1
> Storage: NFS for both primary and secondary
> Reporter: Pavan Kumar Bandarupally
> Assignee: Venkata Siva Vijayendra Bhamidipati
> 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
