[jira] [Comment Edited] (CLOUDSTACK-4475) [ZWPS] attaching an uploaded volume to a VM is always going to first primary storage added
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072927#comment-14072927 ] Anshul Gangwar edited comment on CLOUDSTACK-4475 at 7/24/14 7:28 AM: - fixed by commit aa21cdcd494aff1df119d2e17a3a51da861e3f51 CLOUDSTACK-6897: when we try to attach the uploaded/allocated volume to a VM on zwps, then we were passing the podId of VM instead of storage pool to storage allocator. This resulting in use of Clusterscope storage allocator, allocating a storage pool for VM on zwps beacuse of pod id not null. This was resulting in scope conflict later verified the scenario on hyper-v setup was (Author: anshulg): fixed by commit aa21cdcd494aff1df119d2e17a3a51da861e3f51 CLOUDSTACK-6897: when we try to attach the uploaded/allocated volume to a VM on zwps, then we were passing the podId of VM instead of storage pool to storage allocator. This resulting in use of Clusterscope storage allocator, allocating a storage pool for VM on zwps beacuse of pod id not null. This was resulting in scope conflict later > [ZWPS] attaching an uploaded volume to a VM is always going to first primary > storage added > -- > > Key: CLOUDSTACK-4475 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4475 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, Storage Controller >Affects Versions: 4.2.1 > Environment: vmware esxi 5.1 >Reporter: Srikanteswararao Talluri >Assignee: Anshul Gangwar > Labels: ReleaseNote > Fix For: 4.4.0 > > > Steps to reproduce: > == > 1. Have an advanced zone deployment with two cluster one host and one cluster > scoped primary storage each > 2. add two more zone wide primary storages > 3. create a deployment on zone scoped primary storage > 4. upload a volume. > 5. attach uploaded volume to VM created in step 3. > Observation: > = > While attaching volume, volume is always copied to first available primary > storage in the storage_pool table and as a result attaching a volume created > on cluster scoped primary storage to a VM with its root volume on zone wide > primary storage fails. > 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 | primaryclus1 | 722e6181-8497-3d31-9933-a0a267ae376c | > NetworkFilesystem | 2049 | 1 | 1 | 1 | > 1678552014848 | 590228480 | 10.147.28.7 | NULL | > /export/home/talluri/vmware.campo/primary | 2013-08-23 12:11:12 | NULL > | NULL| Maintenance | DefaultPrimary| CLUSTER | NULL | > 0 | NULL | > | 2 | pimaryclu2 | 9fd9b0fc-c9fd-39b8-8d66-06372c5ff6d2 | > NetworkFilesystem | 2049 | 1 | 1 | 2 | > 1676566495232 | 590228480 | 10.147.28.7 | NULL | > /export/home/talluri/vmware.campo/clus1primary | 2013-08-23 12:18:14 | NULL > | NULL| Up | DefaultPrimary| CLUSTER | NULL | > 0 | NULL | > | 3 | clus1p2 | 22e0c3fe-a390-38fa-8ff7-e1d965a36309 | > NetworkFilesystem | 2049 | 1 | 1 | 1 | > 1660903886848 | 590228480 | 10.147.28.7 | NULL | > /export/home/talluri/vmware.campo/clus1p2 | 2013-08-23 14:30:32 | NULL > | NULL| Up | DefaultPrimary| CLUSTER | NULL | > 0 | NULL | > | 4 | clus1p3 | f2d9fb6b-c433-3c03-acf8-8f73eac48fae | > NetworkFilesystem | 2049 | 1 | 1 | 1 | > 1660901400576 |
[jira] [Comment Edited] (CLOUDSTACK-4475) [ZWPS] attaching an uploaded volume to a VM is always going to first primary storage added
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072927#comment-14072927 ] Anshul Gangwar edited comment on CLOUDSTACK-4475 at 7/24/14 7:26 AM: - fixed by commit aa21cdcd494aff1df119d2e17a3a51da861e3f51 CLOUDSTACK-6897: when we try to attach the uploaded/allocated volume to a VM on zwps, then we were passing the podId of VM instead of storage pool to storage allocator. This resulting in use of Clusterscope storage allocator, allocating a storage pool for VM on zwps beacuse of pod id not null. This was resulting in scope conflict later was (Author: anshulg): fixed by commit aa21cdcd494aff1df119d2e17a3a51da861e3f51 > [ZWPS] attaching an uploaded volume to a VM is always going to first primary > storage added > -- > > Key: CLOUDSTACK-4475 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4475 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Doc, Storage Controller >Affects Versions: 4.2.1 > Environment: vmware esxi 5.1 >Reporter: Srikanteswararao Talluri >Assignee: Anshul Gangwar > Labels: ReleaseNote > Fix For: 4.4.0 > > > Steps to reproduce: > == > 1. Have an advanced zone deployment with two cluster one host and one cluster > scoped primary storage each > 2. add two more zone wide primary storages > 3. create a deployment on zone scoped primary storage > 4. upload a volume. > 5. attach uploaded volume to VM created in step 3. > Observation: > = > While attaching volume, volume is always copied to first available primary > storage in the storage_pool table and as a result attaching a volume created > on cluster scoped primary storage to a VM with its root volume on zone wide > primary storage fails. > 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 | primaryclus1 | 722e6181-8497-3d31-9933-a0a267ae376c | > NetworkFilesystem | 2049 | 1 | 1 | 1 | > 1678552014848 | 590228480 | 10.147.28.7 | NULL | > /export/home/talluri/vmware.campo/primary | 2013-08-23 12:11:12 | NULL > | NULL| Maintenance | DefaultPrimary| CLUSTER | NULL | > 0 | NULL | > | 2 | pimaryclu2 | 9fd9b0fc-c9fd-39b8-8d66-06372c5ff6d2 | > NetworkFilesystem | 2049 | 1 | 1 | 2 | > 1676566495232 | 590228480 | 10.147.28.7 | NULL | > /export/home/talluri/vmware.campo/clus1primary | 2013-08-23 12:18:14 | NULL > | NULL| Up | DefaultPrimary| CLUSTER | NULL | > 0 | NULL | > | 3 | clus1p2 | 22e0c3fe-a390-38fa-8ff7-e1d965a36309 | > NetworkFilesystem | 2049 | 1 | 1 | 1 | > 1660903886848 | 590228480 | 10.147.28.7 | NULL | > /export/home/talluri/vmware.campo/clus1p2 | 2013-08-23 14:30:32 | NULL > | NULL| Up | DefaultPrimary| CLUSTER | NULL | > 0 | NULL | > | 4 | clus1p3 | f2d9fb6b-c433-3c03-acf8-8f73eac48fae | > NetworkFilesystem | 2049 | 1 | 1 | 1 | > 1660901400576 | 590228480 | 10.147.28.7 | NULL | > /export/home/talluri/vmware.campo/clus1p3 | 2013-08-23 14:31:05 | NULL > | NULL| Up | DefaultPrimary| CLUSTER | NULL | > 0 | NULL | > | 5 | clus2p2 | 13bf579c-51f3-317b-893a-98ff6ca8f486 | > NetworkFilesystem | 2049 | 1 | 1 | 2 | > 1660900147200 |
