Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Sat, 10 Aug 2013 07:32:47 +0000 (UTC)
From: "Animesh Chaturvedi (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12662597.1375962269422.39076.1376119967615@arcas>
In-Reply-To: <JIRA.12662597.1375962269422@arcas>
References: <JIRA.12662597.1375962269422@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-4189) [UI] In multi zone setup,
 dedicating a single zone to a domain, shows other zones dedicated as well
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Animesh Chaturvedi updated CLOUDSTACK-4189:
-------------------------------------------

    Assignee:     (was: Animesh Chaturvedi)
    
> [UI] In multi zone setup, dedicating a single zone to a domain, shows other zones dedicated as well
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4189
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4189
>             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: Xenserver
>            Reporter: Saksham Srivastava
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Steps to reproduce:
> 1) Create 2 zone setup z1 and z2,
> 2) Dedicate z1 to domain d1 through UI
> Observed Behavior: UI shows both zones as dedicated.
> The issue is only in UI,
> listDedicatedZone API shows only single zone(z1)
> dedicated_resources table also has the correct entry of the dedicated zone.
> Expected Behavior : Only zone dedicated should be listed as dedicated. 

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