You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Jessica Wang (JIRA)" <ji...@apache.org> on 2014/10/10 00:16:33 UTC
[jira] [Resolved] (CLOUDSTACK-6829) [UI]If no storage is available
for migrate volume UI should popup "no storage available" if you try to
migrate volume
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jessica Wang resolved CLOUDSTACK-6829.
--------------------------------------
Resolution: Not a Problem
This is by design.
"No option in a dropdown" clearly indicates "no item available".
All dropdowns in the whole cloudStack UI work the same way.
> [UI]If no storage is available for migrate volume UI should popup "no storage available" if you try to migrate volume
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6829
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6829
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: UI
> Affects Versions: 4.4.0
> Reporter: prashant kumar mishra
> Assignee: Jessica Wang
> Fix For: 4.4.0
>
> Attachments: screenshot-1.jpg
>
>
> if no storage is available for migration , UI should pop up same message instead empty drop down list .
> steps to repo
> ===========
> 1-prepare a CS setup with one primary storage
> 2-create a volume and attach to vm
> 3-and attach to vm
> 4-try to migrate volume
> Expected
> =======
> since there is no other storage UI should pop up "no storage available"
> Actual
> ======
> UI popup show drop down list of storage with nothing in list
> API
> ====
> http://10.147.38.181:8080/client/api?command=findStoragePoolsForMigration&id=bbedf40d-d2da-40e4-b0d3-55e4a70682d8&response=json&sessionkey=%2B3QBQd4DLtoNPX9sZ%2FfZu2GNiJ8%3D&_=1401779685525
> response
> ------------
> { "findstoragepoolsformigrationresponse" : { } }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)