You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sailaja Mada (JIRA)" <ji...@apache.org> on 2013/05/17 11:31:17 UTC

[jira] [Updated] (CLOUDSTACK-2559) [UI]Resource Name should not be present in UI as it is not available in listASA1000v API response

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

Sailaja Mada updated CLOUDSTACK-2559:
-------------------------------------

    Summary: [UI]Resource Name should not be present in UI as it is not available in listASA1000v API response  (was: [UI]Resource Name should not be present in UI as there it is not available in listASA1000v API response)
    
> [UI]Resource Name should not be present in UI as it is not available in listASA1000v API response
> -------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2559
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2559
>             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: Sailaja Mada
>            Priority: Minor
>
> Setup:Advanced Networking Zone 
> Steps:
> 1. Add ASA instance 
> 2.Access Physical Network -> Network Service provider -> Cisco VNMC -> ASA instances 
> Observation:
> Resource Name should not be present in UI as there it is not available in listASA1000v API response
> <listCiscoAsa1000vResources cloud-stack-version="4.2.0-SNAPSHOT">
> <count>1</count>
> <CiscoAsa1000vResource>
> <resourceid>54ef93d6-4e78-46a5-9863-6276c3494e99</resourceid>
> <hostname>10.102.192.73</hostname>
> <insideportprofile>asa-in</insideportprofile>
> </CiscoAsa1000vResource>
> </listCiscoAsa1000vResources>
> Attached the snap.

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