[jira] [Commented] (CLOUDSTACK-2980) Adding a VLAN range that overlaps with two existing ranges results in inconsistent DB entries

["Saksham Srivastava (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681955#comment-13681955 ] 

Saksham Srivastava commented on CLOUDSTACK-2980:
------------------------------------------------

I would also suggest to keep the vlan ranges always in sorted order as it will ease coalescing of vlan ranges and also the response will be displayed more neatly.
                
> Adding a VLAN range that overlaps with two existing ranges results in inconsistent DB entries
> ---------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2980
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2980
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: Likitha Shetty
>             Fix For: 4.2.0
>
>
> Under PhysicalNetwork - Guest, Add 2 VLAN ranges - 360-369;380-385
> Then adding one new VLAN range, 367-383 results in the following 2 issues, 
> 1. The new range displayed in the UI is 360-383;380-385
> 2. In the DB 'op_dc_vnet_alloc' table every VLAN in the range 370-379 is missing. This is because we are trying to add VLANs from 370-383 and since the entries 380-383 are duplicates the DB insert throws an exception.

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