[jira] [Commented] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740346#comment-13740346
]
Sudha Ponnaganti commented on CLOUDSTACK-2670:
--
pl test this scenario as well
https://issues.apache.org/jira/browse/CLOUDSTACK-3502
> [Object_Store_Refactor] UI/API: migrate volume does not show the available
> primary storages within the cluster
> --
>
> Key: CLOUDSTACK-2670
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.2.0
> Environment: Latest build from object store branch:
> CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
>Reporter: Sanjeev N
>Assignee: Devdeep Singh
>Priority: Critical
> Fix For: 4.2.0
>
>
> Migrate volume does not show the available primary storages within the cluster
> Steps to reproduce:
>
> 1.Bring up CS with xen cluster
> 2.Deploy guest vm
> 3.Add another primary storage to in the cluster
> 4.Stop the vm and try to migrate the root disk to another available primary
> storage in the cluster
> Result:
> ==
> migrate volume called findStoragePoolsFroMigration but the API returned blank
> response:
> http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigration&id=1a4eb56e-4050-4688-b5d7-d721ce4439a2&response=json&sessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D&_=1369391000834
> { "findstoragepoolsformigrationresponse" : { } }
> So migrate volume page displays blank in storage pool drop down list in UI.
--
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
[jira] [Commented] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734561#comment-13734561
]
ASF subversion and git services commented on CLOUDSTACK-2670:
-
Commit 32701f027a9bafca154af7eec7677e7557c911a2 in branch refs/heads/master
from [~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=32701f0 ]
CLOUDSTACK-2670. Migrate volume doesn't allow migration of volumes of a stopped
vm.
The findStoragePoolsForMigration and migrateVolume api were explicitly blocking
moving
a volume if the instance to which it was attached was stopped. Updated the
check for
the same.
> [Object_Store_Refactor] UI/API: migrate volume does not show the available
> primary storages within the cluster
> --
>
> Key: CLOUDSTACK-2670
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.2.0
> Environment: Latest build from object store branch:
> CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
>Reporter: Sanjeev N
>Assignee: Devdeep Singh
>Priority: Critical
> Fix For: 4.2.0
>
>
> Migrate volume does not show the available primary storages within the cluster
> Steps to reproduce:
>
> 1.Bring up CS with xen cluster
> 2.Deploy guest vm
> 3.Add another primary storage to in the cluster
> 4.Stop the vm and try to migrate the root disk to another available primary
> storage in the cluster
> Result:
> ==
> migrate volume called findStoragePoolsFroMigration but the API returned blank
> response:
> http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigration&id=1a4eb56e-4050-4688-b5d7-d721ce4439a2&response=json&sessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D&_=1369391000834
> { "findstoragepoolsformigrationresponse" : { } }
> So migrate volume page displays blank in storage pool drop down list in UI.
--
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
[jira] [Commented] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734474#comment-13734474
]
ASF subversion and git services commented on CLOUDSTACK-2670:
-
Commit 653e2e54a237ef0b26c6685185e41e92b107354a in branch refs/heads/4.2 from
[~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=653e2e5 ]
CLOUDSTACK-2670. Migrate volume doesn't allow migration of volumes of a stopped
vm.
The findStoragePoolsForMigration and migrateVolume api were explicitly blocking
moving
a volume if the instance to which it was attached was stopped. Updated the
check for
the same.
> [Object_Store_Refactor] UI/API: migrate volume does not show the available
> primary storages within the cluster
> --
>
> Key: CLOUDSTACK-2670
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.2.0
> Environment: Latest build from object store branch:
> CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
>Reporter: Sanjeev N
>Assignee: Devdeep Singh
>Priority: Critical
> Fix For: 4.2.0
>
>
> Migrate volume does not show the available primary storages within the cluster
> Steps to reproduce:
>
> 1.Bring up CS with xen cluster
> 2.Deploy guest vm
> 3.Add another primary storage to in the cluster
> 4.Stop the vm and try to migrate the root disk to another available primary
> storage in the cluster
> Result:
> ==
> migrate volume called findStoragePoolsFroMigration but the API returned blank
> response:
> http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigration&id=1a4eb56e-4050-4688-b5d7-d721ce4439a2&response=json&sessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D&_=1369391000834
> { "findstoragepoolsformigrationresponse" : { } }
> So migrate volume page displays blank in storage pool drop down list in UI.
--
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
[jira] [Commented] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734427#comment-13734427
]
Devdeep Singh commented on CLOUDSTACK-2670:
---
The bug should be fixed for 4.2. Increasing the priority.
> [Object_Store_Refactor] UI/API: migrate volume does not show the available
> primary storages within the cluster
> --
>
> Key: CLOUDSTACK-2670
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.2.0
> Environment: Latest build from object store branch:
> CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
>Reporter: Sanjeev N
>Assignee: Devdeep Singh
>Priority: Critical
> Fix For: 4.2.0
>
>
> Migrate volume does not show the available primary storages within the cluster
> Steps to reproduce:
>
> 1.Bring up CS with xen cluster
> 2.Deploy guest vm
> 3.Add another primary storage to in the cluster
> 4.Stop the vm and try to migrate the root disk to another available primary
> storage in the cluster
> Result:
> ==
> migrate volume called findStoragePoolsFroMigration but the API returned blank
> response:
> http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigration&id=1a4eb56e-4050-4688-b5d7-d721ce4439a2&response=json&sessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D&_=1369391000834
> { "findstoragepoolsformigrationresponse" : { } }
> So migrate volume page displays blank in storage pool drop down list in UI.
--
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
[jira] [Commented] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733266#comment-13733266
]
Devdeep Singh commented on CLOUDSTACK-2670:
---
Looking at the issue. Right now the findStoragePoolForMigration and
migrateVolume api is blocking listing of storage pools/migration of volume if
the volume is attached to a stopped vm. I'll fix the code to list appropriate
storage pools and to allow migration of volume if requested.
> [Object_Store_Refactor] UI/API: migrate volume does not show the available
> primary storages within the cluster
> --
>
> Key: CLOUDSTACK-2670
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.2.0
> Environment: Latest build from object store branch:
> CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
>Reporter: Sanjeev N
>Assignee: Devdeep Singh
> Fix For: 4.2.0
>
>
> Migrate volume does not show the available primary storages within the cluster
> Steps to reproduce:
>
> 1.Bring up CS with xen cluster
> 2.Deploy guest vm
> 3.Add another primary storage to in the cluster
> 4.Stop the vm and try to migrate the root disk to another available primary
> storage in the cluster
> Result:
> ==
> migrate volume called findStoragePoolsFroMigration but the API returned blank
> response:
> http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigration&id=1a4eb56e-4050-4688-b5d7-d721ce4439a2&response=json&sessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D&_=1369391000834
> { "findstoragepoolsformigrationresponse" : { } }
> So migrate volume page displays blank in storage pool drop down list in UI.
--
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
[jira] [Commented] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717422#comment-13717422
]
Min Chen commented on CLOUDSTACK-2670:
--
ManagementServerImpl.listStoragePoolsForMigration is implemented by Devdeep
Singh, who should have a better understanding why we have that logic added.
Assign this to him to investigate.
> [Object_Store_Refactor] UI/API: migrate volume does not show the available
> primary storages within the cluster
> --
>
> Key: CLOUDSTACK-2670
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.2.0
> Environment: Latest build from object store branch:
> CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
>Reporter: Sanjeev N
>Assignee: Min Chen
> Fix For: 4.2.0
>
>
> Migrate volume does not show the available primary storages within the cluster
> Steps to reproduce:
>
> 1.Bring up CS with xen cluster
> 2.Deploy guest vm
> 3.Add another primary storage to in the cluster
> 4.Stop the vm and try to migrate the root disk to another available primary
> storage in the cluster
> Result:
> ==
> migrate volume called findStoragePoolsFroMigration but the API returned blank
> response:
> http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigration&id=1a4eb56e-4050-4688-b5d7-d721ce4439a2&response=json&sessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D&_=1369391000834
> { "findstoragepoolsformigrationresponse" : { } }
> So migrate volume page displays blank in storage pool drop down list in UI.
--
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
[jira] [Commented] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13668485#comment-13668485
]
Min Chen commented on CLOUDSTACK-2670:
--
This is the same behavior happening on master, not introduced by object_store
branch. Can you check what is the behavior in master?
> [Object_Store_Refactor] UI/API: migrate volume does not show the available
> primary storages within the cluster
> --
>
> Key: CLOUDSTACK-2670
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.2.0
> Environment: Latest build from object store branch:
> CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
>Reporter: Sanjeev N
>Assignee: Min Chen
> Fix For: 4.2.0
>
>
> Migrate volume does not show the available primary storages within the cluster
> Steps to reproduce:
>
> 1.Bring up CS with xen cluster
> 2.Deploy guest vm
> 3.Add another primary storage to in the cluster
> 4.Stop the vm and try to migrate the root disk to another available primary
> storage in the cluster
> Result:
> ==
> migrate volume called findStoragePoolsFroMigration but the API returned blank
> response:
> http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigration&id=1a4eb56e-4050-4688-b5d7-d721ce4439a2&response=json&sessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D&_=1369391000834
> { "findstoragepoolsformigrationresponse" : { } }
> So migrate volume page displays blank in storage pool drop down list in UI.
--
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
[jira] [Commented] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666723#comment-13666723
]
Min Chen commented on CLOUDSTACK-2670:
--
This behavior is as expected. In current implementation
FindStoragePoolsForMigration we inherited from master branch, it will check if
the volume is attached to a running VM. If the volume id given is not attached
to a running VM, then it will not do migration, so return an empty set.
> [Object_Store_Refactor] UI/API: migrate volume does not show the available
> primary storages within the cluster
> --
>
> Key: CLOUDSTACK-2670
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.2.0
> Environment: Latest build from object store branch:
> CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
>Reporter: Sanjeev N
> Fix For: 4.2.0
>
>
> Migrate volume does not show the available primary storages within the cluster
> Steps to reproduce:
>
> 1.Bring up CS with xen cluster
> 2.Deploy guest vm
> 3.Add another primary storage to in the cluster
> 4.Stop the vm and try to migrate the root disk to another available primary
> storage in the cluster
> Result:
> ==
> migrate volume called findStoragePoolsFroMigration but the API returned blank
> response:
> http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigration&id=1a4eb56e-4050-4688-b5d7-d721ce4439a2&response=json&sessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D&_=1369391000834
> { "findstoragepoolsformigrationresponse" : { } }
> So migrate volume page displays blank in storage pool drop down list in UI.
--
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
[jira] [Commented] (CLOUDSTACK-2670) [Object_Store_Refactor] UI/API: migrate volume does not show the available primary storages within the cluster
[
https://issues.apache.org/jira/browse/CLOUDSTACK-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666191#comment-13666191
]
Sanjeev N commented on CLOUDSTACK-2670:
---
mysql> select * from storage_pool\G;
*** 1. row ***
id: 1
name: pri_xen_os
uuid: c65a038a-750c-3b4f-bf26-7ce3b74e1c85
pool_type: NetworkFilesystem
port: 2049
data_center_id: 1
pod_id: 1
cluster_id: 1
available_bytes: 2815279431680
capacity_bytes: 5902284816384
host_address: 10.147.28.7
user_info: NULL
path: /export/home/sanjeev/pri_xen_os
created: 2013-05-24 12:09:14
removed: NULL
update_time: NULL
status: Up
storage_provider_name: DefaultPrimary
scope: CLUSTER
*** 2. row ***
id: 2
name: pri_xen_os2
uuid: 05820c30-2a0e-33f7-b358-cc9c08864e10
pool_type: NetworkFilesystem
port: 2049
data_center_id: 1
pod_id: 1
cluster_id: 1
available_bytes: 2776974163968
capacity_bytes: 5902284816384
host_address: 10.147.28.7
user_info: NULL
path: /export/home/sanjeev/pri_xen_os2
created: 2013-05-24 15:36:43
removed: NULL
update_time: NULL
status: Up
storage_provider_name: DefaultPrimary
scope: CLUSTER
2 rows in set (0.00 sec)
ERROR:
No query specified
> [Object_Store_Refactor] UI/API: migrate volume does not show the available
> primary storages within the cluster
> --
>
> Key: CLOUDSTACK-2670
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2670
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
>Affects Versions: 4.2.0
> Environment: Latest build from object store branch:
> CloudStack-non-OSS-object_store-47-rhel6.3.tar.gz
>Reporter: Sanjeev N
> Fix For: 4.2.0
>
>
> Migrate volume does not show the available primary storages within the cluster
> Steps to reproduce:
>
> 1.Bring up CS with xen cluster
> 2.Deploy guest vm
> 3.Add another primary storage to in the cluster
> 4.Stop the vm and try to migrate the root disk to another available primary
> storage in the cluster
> Result:
> ==
> migrate volume called findStoragePoolsFroMigration but the API returned blank
> response:
> http://10.147.59.119:8080/client/api?command=findStoragePoolsForMigration&id=1a4eb56e-4050-4688-b5d7-d721ce4439a2&response=json&sessionkey=ixXFsVuKowmsD%2FQeRoCj8INv7Y0%3D&_=1369391000834
> { "findstoragepoolsformigrationresponse" : { } }
> So migrate volume page displays blank in storage pool drop down list in UI.
--
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
