| 2014-09-04 06:18:29 |
Numan Siddique |
description |
Below are the steps to reproduce this issue
$neutron port-create private --fixed-ip ip_address=10.0.0.9 --fixed-ip ip_address=10.0.0.12 --fixed-ip ip_address=10.0.0.14
$nova boot --flavor m1.tiny --image 5b26432d-1671-4ec6-ad98-2e0a33e04dfb --nic port-id=2e91a3d9-bd72-4b88-8422-c2d175d38f98 testt2
The VM testt2 is getting the ip 10.0.0.9
Now create a floating ip and associate it to 10.0.0.14
$ neutron floatingip-associate --fixed-ip-address 10.0.0.14 2cbc2f05-623a-4c79-8938-f831c7594852 2e91a3d9-bd72-4b88-8422-c2d175d38f98
$ neutron floatingip-list
+--------------------------------------+------------------+---------------------+--------------------------------------+
| id | fixed_ip_address | floating_ip_address | port_id |
+--------------------------------------+------------------+---------------------+--------------------------------------+
| 0c59f74b-9170-4a6c-83f3-b46dd899a4fb | 10.0.0.5 | 172.168.0.2 | ba9072e4-2a4a-47e9-988f-75940c3bb80f |
| 2cbc2f05-623a-4c79-8938-f831c7594852 | 10.0.0.14 | 172.168.0.3 | 2e91a3d9-bd72-4b88-8422-c2d175d38f98 |
+--------------------------------------+------------------+---------------------+--------------------------------------+
$ nova list
+--------------------------------------+--------+--------+------------+-------------+-------------------------------------------------------------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+--------+--------+------------+-------------+-------------------------------------------------------------------------------+
| 76d3d82c-a577-4b88-b699-fbf2f1aab137 | test | ACTIVE | - | Running | private=10.0.0.3, 172.168.0.2 |
| 9404c929-425d-4e04-8ce5-b765565e7dc8 | testt2 | ACTIVE | - | Running | private=10.0.0.14, 10.0.0.9, 10.0.0.12, 172.168.0.3, 172.168.0.3, 172.168.0.3 |
+--------------------------------------+--------+--------+------------+-------------+-------------------------------------------------------------------------------+
I am able to ping to the floating ip 172.168.0.3 which is not the case when i test with the ML2/OVS plugin.
Looks like floating ip is getting associated to all the ip addresses of a port. |
Below are the steps to reproduce this issue
$neutron port-create private --fixed-ip ip_address=10.0.0.9 --fixed-ip ip_address=10.0.0.12 --fixed-ip ip_address=10.0.0.14
$nova boot --flavor m1.tiny --image 5b26432d-1671-4ec6-ad98-2e0a33e04dfb --nic port-id=2e91a3d9-bd72-4b88-8422-c2d175d38f98 testt2
The VM testt2 is getting the ip 10.0.0.9
Now create a floating ip and associate it to 10.0.0.14
$ neutron floatingip-associate --fixed-ip-address 10.0.0.14 2cbc2f05-623a-4c79-8938-f831c7594852 2e91a3d9-bd72-4b88-8422-c2d175d38f98
$ neutron floatingip-list
+--------------------------------------+------------------+---------------------+--------------------------------------+
| id | fixed_ip_address | floating_ip_address | port_id |
+--------------------------------------+------------------+---------------------+--------------------------------------+
| 0c59f74b-9170-4a6c-83f3-b46dd899a4fb | 10.0.0.5 | 172.168.0.2 | ba9072e4-2a4a-47e9-988f-75940c3bb80f |
| 2cbc2f05-623a-4c79-8938-f831c7594852 | 10.0.0.14 | 172.168.0.3 | 2e91a3d9-bd72-4b88-8422-c2d175d38f98 |
+--------------------------------------+------------------+---------------------+--------------------------------------+
$ nova list
+--------------------------------------+--------+--------+------------+-------------+-------------------------------------------------------------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+--------+--------+------------+-------------+-------------------------------------------------------------------------------+
| 76d3d82c-a577-4b88-b699-fbf2f1aab137 | test | ACTIVE | - | Running | private=10.0.0.3, 172.168.0.2 |
| 9404c929-425d-4e04-8ce5-b765565e7dc8 | testt2 | ACTIVE | - | Running | private=10.0.0.14, 10.0.0.9, 10.0.0.12, 172.168.0.3, 172.168.0.3, 172.168.0.3 |
+--------------------------------------+--------+--------+------------+-------------+-------------------------------------------------------------------------------+
I am able to ping to the floating ip 172.168.0.3 which is not the case when i test with the ML2/OVS plugin.
Looks like floating ip is getting associated to all the ip addresses of a port.
Below is the nova list output on the Ml2/ovs devstack
~$ nova list
+--------------------------------------+----------+--------+------------+-------------+------------------------------------------+
| ID | Name | Status | Task State | Power State | Networks |
+--------------------------------------+----------+--------+------------+-------------+------------------------------------------+
| 692b723a-31f4-460a-83e6-1baffc3246bb | flttest1 | ACTIVE | - | Running | private=10.0.0.10, 10.0.0.12, 172.24.4.3 |
| dbd87bd2-adbe-4c56-a345-cd8cfbb6b645 | flttest2 | ACTIVE | - | Running | private=10.0.0.11, 172.24.4.4 |
+--------------------------------------+----------+--------+------------+-------------+------------------------------------------+ |
|
