yahoo-eng-team team mailing list archive

[OpenStack Infra <1599089@xxxxxxxxxxxxxxxxxx>]

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 <obondarev@xxxxxxxxxxxx>
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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1599089

Title:
  DVR: floating ip stops working after reassignment

Status in neutron:
  Fix Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1599089/+subscriptions