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

Sailaja Mada closed CLOUDSTACK-4474.
------------------------------------


This is fixed with latest build. Hence closing the bug. 
                
> [UI] Zone wide Primary storages does not display the zone information
> ---------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4474
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4474
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: UI
>    Affects Versions: 4.2.1
>            Reporter: Sailaja Mada
>            Assignee: Jessica Wang
>            Priority: Critical
>             Fix For: 4.2.1
>
>         Attachments: dbvol.sql, zonewide1.png, zonewide2.png
>
>
> Steps:
> 1. Configure Adv Zone with VMWARE cluster 
> 2. Add Zone wide primary zone 
> 3. Access Infrastructure->Primary Storage's 
> 4. Try to get the Zone with which this storage is added.  
> Observation:
> There is no zone info provided with this storage :
> API gives the details of the zone :
> http://10.102.192.207:8080/client/api?command=listStoragePools&sessionkey=W20AJSGGax%2F%2B4ASviTMmxq26fx0%3D&page=1&pageSize=20&listAll=true&_=1377257345005
> <storagepool><id>f528f6ca-31e0-333a-88a1-93acce50e381</id><zoneid>659f6614-3363-46eb-ace3-6d1007957d30</zoneid><zonename>LegacyZone1</zonename><name>legacyzwps2</name><ipaddress>10.102.192.100</ipaddress><path>/cpg_vol/sailaja/legacyzwps2</path><created>2013-08-22T12:10:42+0530</created><type>NetworkFilesystem</type><disksizetotal>879609303040</disksizetotal><disksizeallocated>10737418240</disksizeallocated><disksizeused>491180085248</disksizeused><tags>zwps2</tags><state>Up</state><scope>ZONE</scope><hypervisor>VMware</hypervisor></storagepool><storagepool>
>   

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

Reply via email to