[
https://issues.apache.org/jira/browse/CLOUDSTACK-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkata swamybabu budumuru closed CLOUDSTACK-2960.
--------------------------------------------------
verified on the latest build. It now checks if there is any existing VLAN with
same id and if yes then it fails with error.
"Found a VLAN id 44 already existing in zone
ee59c45f-4ad0-4907-bf06-1c098633e728 that conflicts with VLAN id of the
portable ip range being configured"
> [portableIPrange] CS should check the portable ip range, vlan with existing
> public ip ranges and vlans
> -------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2960
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2960
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Affects Versions: 4.2.0
> Environment: commit id # 673b293d75419a4b76379092db2b204cdc6160a4
> Reporter: venkata swamybabu budumuru
> Assignee: Murali Reddy
> Fix For: 4.2.0
>
>
> Steps to reproduce :
> 1. Have latest cloudstack setup with at least one adv zone.
> 2. Have the following public ip range already added
> start ip : 10.147.44.80
> end ip : 10.147.44.89
> gw : 10.147.44.1
> mask : 255.255.255.0
> VLAN : 44
> 3. Add the same above range including vlan to the portable ip range
> Observations:
> (i) This goes fine without any issues.
> (ii) Allowing the above will create issue when user tries to have the same ip
> from public ip range and portable ip range on the same router.
> Attaching all the required logs and db dump to the bug.
--
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
