FIP and router iptables are not updated when associated port ip address is changed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Expired
|
Undecided
|
Unassigned |
Bug Description
Newton,
[root@controller-0 ~]# rpm -qa | grep neutron
python-
puppet-
python-
openstack-
openstack-
openstack-
openstack-
openstack-
We have a VM with FIP associated to it.
[stack@undercloud-0 ~]$ nova list
+------
| ID | Name | Status | Task State | Power State | Networks |
+------
| 1fe84939-
+------
[stack@undercloud-0 ~]$ neutron floatingip-show a009ff12-
+------
| Field | Value |
+------
| created_at | 2016-11-
| description | |
| fixed_ip_address | 192.168.0.7 | <<<----
| floating_ip_address | 10.0.0.211 |
| floating_network_id | 7e09c182-
| id | a009ff12-
| port_id | 7d749eb0-
| project_id | af788c6da1fb438
| revision_number | 4 |
| router_id | 9696bdb2-
| status | ACTIVE |
| tenant_id | af788c6da1fb438
| updated_at | 2016-11-
+------
After updating the VMport:
openstack port set parent_port --fixed-ip subnet=
openstack port unset parent_port --fixed-ip subnet=
The FIP remained the same and the IP was not changed from 192.168.0.7 to 192.168.0.55.
The connectivity to the VM was lost due to unchanged iptable rules on the router
[root@controller-0 ~]# ip net e qrouter-
SNAT all -- 192.168.0.7 anywhere to:10.0.0.211 <<<-------------
We should have the iptables rule and FIP updated automatically. Connectivity should not be lost.
Can you paste the output from a port-show for that port?
Did the neutron-server log any errors?
Did the l3-agent log any errors?