cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wei Zhou (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-1668) IP conflict in VPC tier
Date Tue, 19 Mar 2013 19:07:15 GMT

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

Wei Zhou commented on CLOUDSTACK-1668:
--------------------------------------

Chip, 

The patch is for 4.0.1 only. However, this issue exists in master and 4.1 actually. I will
create a new patch for master/4.1
                
> 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

Mime
View raw message