You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "angeline shen (JIRA)" <ji...@apache.org> on 2013/06/07 04:04:19 UTC

[jira] [Updated] (CLOUDSTACK-2888) PVLAN - Ubuntu 13.04 vmware - should not allow networks with different primary VLAN with same Secondary VLAN, same primary VLAN with different Secondary VLAN

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

angeline shen updated CLOUDSTACK-2888:
--------------------------------------

    Attachment: management-server.log.gz
    
> PVLAN - Ubuntu 13.04   vmware  - should not allow networks with different primary VLAN  with same Secondary VLAN, same primary VLAN with different Secondary VLAN 
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2888
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2888
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>         Environment: MS ASF 4.2 build CloudStack-non-OSS-MASTER-452-rhel6.3.tar.gz
> vmware ESXi 5.0 hosts 
> ubuntu 13.04       hosts
>            Reporter: angeline shen
>            Assignee: Venkata Siva Vijayendra Bhamidipati
>             Fix For: 4.2.0
>
>         Attachments: management-server.log.gz
>
>
> Given:
> pvlan1  = 1611            svlan1 = 998
> pvlan2  = 1612            svlan2 = 997
>                             nonexistent   svlan3 = 999
> Following  PVLAN networks  SHOULD NOT HAVE BEEN ALLOWED to be created :
> pvlan1 ,  svlan2 
> pvlan1 ,  svlan3  
> pvlan2 ,  svlan1
> pvlan2 ,  svlan3
> Result:   Above PVLAN networks were allowed to be created

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