yahoo-eng-team team mailing list archive

[Huang Cheng <1760029@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Related to: Bug #1745572

The binding loop still exists due to the mistaken comparison as below.

https://pastebin.com/RRFX8YfG

The value 1 refers to the segmentation_id of a "segment" object (e.g., vxlan vni, vlan tag).
The value 2 refers to the uuid of a "segment" object, which will be persisted as ml2_port_binding_levels.segment_id after the binding process.

** Affects: neutron
     Importance: Undecided
     Assignee: Huang Cheng (hcpedh)
         Status: New


** Tags: binding hierarchical ml2 port

** Description changed:

  Related to: Bug #1745572
  
  The binding loop still exists due to the mistaken comparison as below.
  
-     def _check_driver_to_bind(self, driver, segments_to_bind, binding_levels):
-         segment_ids_to_bind = {s[api.SEGMENTATION_ID]                            # value 1
-                                for s in segments_to_bind}
-         for level in binding_levels:
-             if (level.driver == driver.name and
-                     level.segment_id in segment_ids_to_bind):                    # value 2
-                 LOG.debug("segment %(segment)s is already bound "
-                           "by driver %(driver)s",
-                           {"segment": level.segment_id,
-                            "driver": level.driver})
-                 return False
-         return True
+ https://pastebin.com/RRFX8YfG
  
  The value 1 refers to the segmentation_id of a "segment" object (e.g., vxlan vni, vlan tag).
  The value 2 refers to the uuid of a "segment" object, which will be persisted as ml2_port_binding_levels.segment_id after the binding process.

** Changed in: neutron
     Assignee: (unassigned) => Huang Cheng (hcpedh)

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

Title:
  ml2 hierarchical port binding cause binding loop

Status in neutron:
  New

Bug description:
  Related to: Bug #1745572

  The binding loop still exists due to the mistaken comparison as below.

  https://pastebin.com/RRFX8YfG

  The value 1 refers to the segmentation_id of a "segment" object (e.g., vxlan vni, vlan tag).
  The value 2 refers to the uuid of a "segment" object, which will be persisted as ml2_port_binding_levels.segment_id after the binding process.

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