Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 6 Jun 2013 09:54:20 +0000 (UTC)
From: "Devdeep Singh (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12649883.1369827686341.77282.1370512460469@arcas>
In-Reply-To: <JIRA.12649883.1369827686341@arcas>
References: <JIRA.12649883.1369827686341@arcas>
Subject: [jira] [Assigned] (CLOUDSTACK-2734) [SXM][UI]: storage pools which
 are not suitable for migration should not be listed for a volume
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Devdeep Singh reassigned CLOUDSTACK-2734:
-----------------------------------------

    Assignee: Devdeep Singh
    
> [SXM][UI]: storage pools which are not suitable for migration should not be listed for a volume
> -----------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2734
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2734
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.2.0
>            Reporter: Srikanteswararao Talluri
>            Assignee: Devdeep Singh
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Steps to reproduce:
> 1. Add primary storage pool P1 and P2 with tags "testpool" and P3, P4 without any tags
> 2. create a disk offering D1 to use this tag "testpool"
> 3. create a volume V1 by selecting disk offering D1.
> 4. Now,click on the migrateVolume
> Step 4, lists all primary storage pools but it shows P1& P2 as suitable  and P3&P4 as not suitable.
> Expected behaviour: 
> When P3 and P4 are not suitable for migration, don't show them at all.

--
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