No seg id for router port

Bug #1444455 reported by Eran Gampel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
DragonFlow
Fix Released
Critical
Eran Gampel

Bug Description

The port data is not inserted into the l3_app because it is missing the segmentation id

It seem to be a BUG related to the change of the router type to DVR to support the centralize SNAT

Changed in dragonflow:
importance: Undecided → Critical
assignee: nobody → Eran Gampel (eran-gampel)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to dragonflow (master)

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

Changed in dragonflow:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to dragonflow (master)

Reviewed: https://review.openstack.org/173765
Committed: https://git.openstack.org/cgit/stackforge/dragonflow/commit/?id=64f93c5375512604a86758f21e6b192cb26bbd12
Submitter: Jenkins
Branch: master

commit 64f93c5375512604a86758f21e6b192cb26bbd12
Author: Gal Sagie <email address hidden>
Date: Wed Apr 15 13:41:35 2015 +0300

    Add segmentation_id to router port

    Use VM port segmentation_id to update router port
    Partial-Bug: #1444455

    Change-Id: Iacf45c4bb522b48ae12d18b17419a35ead8b11d6

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Reviewed: https://review.openstack.org/173840
Committed: https://git.openstack.org/cgit/stackforge/dragonflow/commit/?id=c9c296fd531f818d6ba2dc8221347547ea3c9b76
Submitter: Jenkins
Branch: master

commit c9c296fd531f818d6ba2dc8221347547ea3c9b76
Author: eran gampel <email address hidden>
Date: Wed Apr 15 14:35:25 2015 +0300

    It seem that this BUG is related to the change of the router type to DVR in order to support the centralize SNAT
    We will need to check if this is a bug in neutron or by design but the
    router port is missing the segmentation id data
    To overcome this is issue we send additional arp notify for each new
    port
    for the router port on the same subnet, this will double the number of
    arp notify RPC messages to the agent messages but this is the only way
    to fix it from outside of neutron

    Close-Bug: #1444455

    Change-Id: I7591691125d83881d88c155aa11b803f9e79c731

Changed in dragonflow:
status: In Progress → Confirmed
Changed in dragonflow:
status: Confirmed → Fix Committed
Omer Anson (omer-anson)
Changed in dragonflow:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.