[
https://issues.apache.org/jira/browse/CLOUDSTACK-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607096#comment-13607096
]
ASF subversion and git services commented on CLOUDSTACK-1668:
-------------------------------------------------------------
Commit 0ce1d4fde1fb9e68ed83a9e094133701abbee291 in branch refs/heads/4.1 from
[~weizhou]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=0ce1d4f ]
CLOUDSTACK-1668: Fix IP conflict in VPC tier
Currently, allPossibleIps return the Ip lists which include the gateway,
so we need to remove gateway ip from this list.
Now, for non-VPC network it works, because NetUtils.getAllIpsFromCidr
return the Ip lists which do not include the first IP of the network
(like 192.168.0.1).
We need too add the first IP into the returned Ip list, because it can
be used for VM if it is not the gateway IP (for example, VPC networks).
The corresponding patch for 4.0.1 has been posted on
https://reviews.apache.org/r/9923/
Signed-off-by: Chip Childers <chip.child...@gmail.com>
> IP conflict in VPC tier
> -----------------------
>
> Key: CLOUDSTACK-1668
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1668
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.0.1, 4.1.0
> Reporter: Wei Zhou
> Assignee: Wei Zhou
> Priority: Critical
> Attachments: ipaddress=gatewayip.jpg
>
>
> The first instance in a VPC tier may have a same IP address to gateway of the
> tier.
> It is because the instance NIC is created before the gateway NIC.
> For example,
> mysql> select * from nics where network_id=240;
> +-----+--------------------------------------+-------------+-------------------+----------------+-----------------+----------------+---------+---------------+------------+------+----------+----------+--------------------------+--------------------------------------+-----------+---------------------+---------------+-------------+-------------+--------------+---------------------+---------+
> | id | uuid | instance_id | mac_address
> | ip4_address | netmask | gateway | ip_type |
> broadcast_uri | network_id | mode | state | strategy | reserver_name
> | reservation_id | device_id | update_time
> | isolation_uri | ip6_address | default_nic | vm_type | created
> | removed |
> +-----+--------------------------------------+-------------+-------------------+----------------+-----------------+----------------+---------+---------------+------------+------+----------+----------+--------------------------+--------------------------------------+-----------+---------------------+---------------+-------------+-------------+--------------+---------------------+---------+
> | 348 | 2c4fd128-c2f9-4862-a870-10b408282a08 | 182 |
> 02:00:7d:eb:00:01 | 192.168.101.52 | 255.255.255.240 | 192.168.101.60 | Ip4
> | vlan://610 | 240 | Dhcp | Reserved | Start |
> ExternalGuestNetworkGuru | 3f23d820-5b81-48bd-8c04-ec53d8a20f8d | 0 |
> 2013-03-13 21:36:11 | vlan://610 | NULL | 1 | User
> | 2013-03-13 20:36:04 | NULL |
> | 349 | 5c71231d-09a8-4ece-81a2-9458966e3e0b | 175 |
> 02:00:4e:d2:00:02 | 192.168.101.60 | 255.255.255.240 | 192.168.101.60 | Ip4
> | vlan://610 | 240 | Dhcp | Reserved | Start |
> ExternalGuestNetworkGuru | NULL | 3 |
> 2013-03-13 21:36:04 | vlan://610 | NULL | 0 |
> DomainRouter | 2013-03-13 20:36:04 | NULL |
> +-----+--------------------------------------+-------------+-------------------+----------------+-----------------+----------------+---------+---------------+------------+------+----------+----------+--------------------------+--------------------------------------+-----------+---------------------+---------------+-------------+-------------+--------------+---------------------+---------+
> 192.168.101.52 is the Guest IP.
> 192.168.101.60 is the Gateway IP.
--
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
