[jira] [Updated] (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:all-tabpanel ] Rajesh Battala updated CLOUDSTACK-4475: --- Priority: Major (was: Critical) [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 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 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p2 | 2013-08-23 14:31:38 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 7 | clus2p3 | 294ae9ff-cb02-33a0-8f31-21fdd8ff34db | NetworkFilesystem | 2049 | 1 | 1 | 2 | 1660894195712 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p3 | 2013-08-23 14:33:03 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 8 | z1 |
[jira] [Updated] (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:all-tabpanel ] Rajesh Battala updated CLOUDSTACK-4475: --- Priority: Critical (was: Major) [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 Priority: Critical 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 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p2 | 2013-08-23 14:31:38 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 7 | clus2p3 | 294ae9ff-cb02-33a0-8f31-21fdd8ff34db | NetworkFilesystem | 2049 | 1 | 1 | 2 | 1660894195712 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p3 | 2013-08-23 14:33:03 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 8 | z1
[jira] [Updated] (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:all-tabpanel ] edison su updated CLOUDSTACK-4475: -- Assignee: (was: edison su) [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 Labels: ReleaseNote Fix For: 4.3.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 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p2 | 2013-08-23 14:31:38 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 7 | clus2p3 | 294ae9ff-cb02-33a0-8f31-21fdd8ff34db | NetworkFilesystem | 2049 | 1 | 1 | 2 | 1660894195712 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p3 | 2013-08-23 14:33:03 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 8 | z1 |
[jira] [Updated] (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:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-4475: --- Fix Version/s: (was: 4.2.1) 4.3.0 [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: edison su Labels: ReleaseNote Fix For: 4.3.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 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p2 | 2013-08-23 14:31:38 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 7 | clus2p3 | 294ae9ff-cb02-33a0-8f31-21fdd8ff34db | NetworkFilesystem | 2049 | 1 | 1 | 2 | 1660894195712 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p3 | 2013-08-23 14:33:03 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0
[jira] [Updated] (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:all-tabpanel ] Ram Ganesh updated CLOUDSTACK-4475: --- Labels: ReleaseNote (was: ) [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: Storage Controller Affects Versions: 4.2.1 Environment: vmware esxi 5.1 Reporter: Srikanteswararao Talluri Assignee: edison su Labels: ReleaseNote Fix For: 4.2.1 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 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p2 | 2013-08-23 14:31:38 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 7 | clus2p3 | 294ae9ff-cb02-33a0-8f31-21fdd8ff34db | NetworkFilesystem | 2049 | 1 | 1 | 2 | 1660894195712 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p3 | 2013-08-23 14:33:03 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 8 | z1 |
[jira] [Updated] (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:all-tabpanel ] Ram Ganesh updated CLOUDSTACK-4475: --- Component/s: Doc [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: edison su Labels: ReleaseNote Fix For: 4.2.1 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 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p2 | 2013-08-23 14:31:38 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 7 | clus2p3 | 294ae9ff-cb02-33a0-8f31-21fdd8ff34db | NetworkFilesystem | 2049 | 1 | 1 | 2 | 1660894195712 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p3 | 2013-08-23 14:33:03 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 8 | z1 |
[jira] [Updated] (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:all-tabpanel ] edison su updated CLOUDSTACK-4475: -- Status: Open (was: Ready To Review) [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: Storage Controller Affects Versions: 4.2.1 Environment: vmware esxi 5.1 Reporter: Srikanteswararao Talluri Assignee: edison su Fix For: 4.2.1 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 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p2 | 2013-08-23 14:31:38 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 7 | clus2p3 | 294ae9ff-cb02-33a0-8f31-21fdd8ff34db | NetworkFilesystem | 2049 | 1 | 1 | 2 | 1660894195712 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p3 | 2013-08-23 14:33:03 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 8 | z1 |
[jira] [Updated] (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:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-4475: --- Priority: Major (was: Critical) [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: Storage Controller Affects Versions: 4.2.1 Environment: vmware esxi 5.1 Reporter: Srikanteswararao Talluri Assignee: edison su Fix For: 4.2.1 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 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p2 | 2013-08-23 14:31:38 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 7 | clus2p3 | 294ae9ff-cb02-33a0-8f31-21fdd8ff34db | NetworkFilesystem | 2049 | 1 | 1 | 2 | 1660894195712 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p3 | 2013-08-23 14:33:03 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 8 | z1 |
[jira] [Updated] (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:all-tabpanel ] Rajesh Battala updated CLOUDSTACK-4475: --- Status: Ready To Review (was: In Progress) [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: Storage Controller Affects Versions: 4.2.1 Environment: vmware esxi 5.1 Reporter: Srikanteswararao Talluri Assignee: Rajesh Battala Priority: Critical Fix For: 4.2.1 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 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p2 | 2013-08-23 14:31:38 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 7 | clus2p3 | 294ae9ff-cb02-33a0-8f31-21fdd8ff34db | NetworkFilesystem | 2049 | 1 | 1 | 2 | 1660894195712 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p3 | 2013-08-23 14:33:03 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL |
[jira] [Updated] (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:all-tabpanel ] Rajesh Battala updated CLOUDSTACK-4475: --- Assignee: Rajesh Battala (was: edison su) [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: Storage Controller Affects Versions: 4.2.1 Environment: vmware esxi 5.1 Reporter: Srikanteswararao Talluri Assignee: Rajesh Battala Priority: Critical Fix For: 4.2.1 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 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p2 | 2013-08-23 14:31:38 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | | 7 | clus2p3 | 294ae9ff-cb02-33a0-8f31-21fdd8ff34db | NetworkFilesystem | 2049 | 1 | 1 | 2 | 1660894195712 | 590228480 | 10.147.28.7 | NULL | /export/home/talluri/vmware.campo/clus2p3 | 2013-08-23 14:33:03 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | |
