Sanjeev N created CLOUDSTACK-3241:
-------------------------------------
Summary: [Multiple_IP_Ranges] Adding ip range fails if there are
two IP ranges existing in two different CIDRs
Key: CLOUDSTACK-3241
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3241
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: Latest build from master-6-17-stable branch
Reporter: Sanjeev N
Priority: Critical
Fix For: 4.2.0
Adding ip range fails if there are two IP ranges existing in two different CIDRs
Steps to Reproduce:
==================
1.Bring up CS in Advanced/Basic zone
2.Add guest ip range in shared network
eg: 10.147.33.3-10.147.33.10 GW: 10.147.33.1 Netmask: 255.255.255.128
3.Add another guest ip range in new CIDR in the same shared network
eg: 10.147.33.130-10.147.33.135 GW: 10.147.33.129 Netmask: 255.255.255.192
4. Now try to add another ip range without overlapping with any of the existing
ip ranges in the first CIDR added at step2
Expected Result:
==============
Adding ip range should succeed
Actual Result:
============
Adding ip range failed
Observations:
============
Adding ip range failed with following error message:
"Please ensure that your start IP is in the same subnet as your IP range's
gateway, as per the IP range's netmask."
Following are the IP ranges existing in the shared network;
mysql> select * from vlan where data_center_id=3 and vlan_type='DirectAttached';
+----+--------------------------------------+---------+---------------+-----------------+-----------------------------+----------------+----------------+------------+---------------------+-------------+----------+-----------+
| id | uuid | vlan_id | vlan_gateway |
vlan_netmask | description | vlan_type | data_center_id
| network_id | physical_network_id | ip6_gateway | ip6_cidr | ip6_range |
+----+--------------------------------------+---------+---------------+-----------------+-----------------------------+----------------+----------------+------------+---------------------+-------------+----------+-----------+
| 15 | 471afecc-0afb-4f81-a5e3-c7bbbfd82a79 | 33 | 10.147.33.1 |
255.255.255.128 | 10.147.33.10-10.147.33.15 | DirectAttached | 3
| 214 | 202 | NULL | NULL | NULL |
| 19 | ecc7fb7d-91bb-4b24-99fc-7b05746f05bb | 33 | 10.147.33.129 |
255.255.255.192 | 10.147.33.130-10.147.33.135 | DirectAttached | 3
| 214 | 202 | NULL | NULL | NULL |
+----+--------------------------------------+---------+---------------+-----------------+-----------------------------+----------------+----------------+------------+---------------------+-------------+----------+-----------+
2 rows in set (0.00 sec)
Adding another ip range with following details failed with the error message
mentioned above:
http://10.147.59.119:8080/client/api?command=createVlanIpRange&forVirtualNetwork=false&networkid=67f79628-b134-427a-a3ea-a510c8c8d320&gateway=10.147.33.1&netmask=255.255.255.128&startip=10.147.33.20&endip=10.147.33.25&response=json&sessionkey=O28i4PL9tPWGlRWnkZs462BkqpA%3D&_=1372335419908
--
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
