DVR: floating ip stops working after reassignment

Bug #1599089 reported by Oleg Bondarev on 2016-07-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
High
Oleg Bondarev

Bug Description

When reassigning floating IP from one VM to another on the same host, it stops responding. This happens due to l3 agent just checks that IP address is configured on the interface and does not update ip rules to reflect new fixed IP.

Reassignment works if disassociate floating IP first and then associate it with another fixed IP.
However API allows reassignment without disassociation so it should work as well.

tags: added: mitaka-backport-potential
tags: added: liberty-backport-potential

Fix proposed to branch: master
Review: https://review.openstack.org/337591

Changed in neutron:
status: New → In Progress
Changed in neutron:
importance: Undecided → High

Reviewed: https://review.openstack.org/337591
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b8a2cb813225ae6178f34363cab9a2446d471472
Submitter: Jenkins
Branch: master

commit b8a2cb813225ae6178f34363cab9a2446d471472
Author: Oleg Bondarev <email address hidden>
Date: Tue Jul 5 12:15:03 2016 +0300

    DVR: handle floating IP reassociation on the same host

    The case when floating IP is reassociated from one VM to another
    on the same host without doing disassociation, was not properly handled:
    l3 dvr agent only checked that the floating address was present on the
    device in router namespace and considered floating IP confiigured correctly.
    This patch adds fip_mapping to router object so fixed IP change can be
    detected and handled.

    Closes-Bug: #1599089
    Change-Id: I25c23bb9ad7b9a9b90f225f37417142e2304deb8

Changed in neutron:
status: In Progress → Fix Released

Reviewed: https://review.openstack.org/341848
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1b9168be872d4f17236ef085a70cf2d152c5a217
Submitter: Jenkins
Branch: stable/liberty

commit 1b9168be872d4f17236ef085a70cf2d152c5a217
Author: Oleg Bondarev <email address hidden>
Date: Tue Jul 5 12:15:03 2016 +0300

    DVR: handle floating IP reassociation on the same host

    The case when floating IP is reassociated from one VM to another
    on the same host without doing disassociation, was not properly handled:
    l3 dvr agent only checked that the floating address was present on the
    device in router namespace and considered floating IP confiigured correctly.
    This patch adds fip_mapping to router object so fixed IP change can be
    detected and handled.

    Closes-Bug: #1599089
    (cherry picked from commit b8a2cb813225ae6178f34363cab9a2446d471472)

    Conflicts:
     neutron/tests/functional/agent/l3/test_dvr_router.py
    Change-Id: I25c23bb9ad7b9a9b90f225f37417142e2304deb8

tags: added: in-stable-liberty
tags: added: in-stable-mitaka

Reviewed: https://review.openstack.org/341840
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=251d6803eb65b54d75f6eedaabc83321e194cbc3
Submitter: Jenkins
Branch: stable/mitaka

commit 251d6803eb65b54d75f6eedaabc83321e194cbc3
Author: Oleg Bondarev <email address hidden>
Date: Tue Jul 5 12:15:03 2016 +0300

    DVR: handle floating IP reassociation on the same host

    The case when floating IP is reassociated from one VM to another
    on the same host without doing disassociation, was not properly handled:
    l3 dvr agent only checked that the floating address was present on the
    device in router namespace and considered floating IP confiigured correctly.
    This patch adds fip_mapping to router object so fixed IP change can be
    detected and handled.

    Closes-Bug: #1599089
    (cherry picked from commit b8a2cb813225ae6178f34363cab9a2446d471472)

    Conflicts:
     neutron/tests/functional/agent/l3/test_dvr_router.py
    Change-Id: I25c23bb9ad7b9a9b90f225f37417142e2304deb8

tags: added: neutron-proactive-backport-potential

This issue was fixed in the openstack/neutron 7.1.2 release.

This issue was fixed in the openstack/neutron 8.2.0 release.

This issue was fixed in the openstack/neutron 9.0.0.0b3 development milestone.

tags: removed: liberty-backport-potential mitaka-backport-potential neutron-proactive-backport-potential
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers