Uploaded image for project: 'OpenFlowPlugin'
  1. OpenFlowPlugin
  2. OPNFLWPLUG-832

Flow ID not updated in operational after removing and adding a flow with same match

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Done
    • None
    • None
    • General
    • None
    • Operating System: All
      Platform: All

    • 7349

    Description

      This is only seen in Beryllium. To reproduce:

      1) Push regular flow:

      <flow xmlns="urn:opendaylight:flow:inventory">
      <id>285</id>
      <instructions>
      <instruction>
      <order>0</order>
      <apply-actions>
      <action>
      <order>0</order>
      <output-action>
      <output-node-connector>2</output-node-connector>
      </output-action>
      </action>
      </apply-actions>
      </instruction>
      </instructions>
      <hard-timeout>0</hard-timeout>
      <match>
      <ethernet-match>
      <ethernet-type>
      <type>2048</type>
      </ethernet-type>
      </ethernet-match>
      <ipv4-destination>10.0.10.0/24</ipv4-destination>
      </match>
      <flow-name>flow1</flow-name>
      <priority>162</priority>
      <table_id>0</table_id>
      <idle-timeout>0</idle-timeout>
      </flow>

      2) Delete and Push same flow with different ID (286) with no pause in between:

      <flow xmlns="urn:opendaylight:flow:inventory">
      <id>286</id>
      <instructions>
      <instruction>
      <order>0</order>
      <apply-actions>
      <action>
      <order>0</order>
      <output-action>
      <output-node-connector>2</output-node-connector>
      </output-action>
      </action>
      </apply-actions>
      </instruction>
      </instructions>
      <hard-timeout>0</hard-timeout>
      <match>
      <ethernet-match>
      <ethernet-type>
      <type>2048</type>
      </ethernet-type>
      </ethernet-match>
      <ipv4-destination>10.0.10.0/24</ipv4-destination>
      </match>
      <flow-name>flow1</flow-name>
      <priority>162</priority>
      <table_id>0</table_id>
      <idle-timeout>0</idle-timeout>
      </flow>

      3) Check operational flow has the old ID (285):

      <?xml version="1.0" encoding="UTF-8"?>
      <flow>
      <id>285</id>
      <instructions>
      <instruction>
      <order>0</order>
      <apply-actions>
      <action>
      <order>0</order>
      <output-action>
      <output-node-connector>2</output-node-connector>
      <max-length>0</max-length>
      </output-action>
      </action>
      </apply-actions>
      </instruction>
      </instructions>
      <cookie>0</cookie>
      <match>
      <ethernet-match>
      <ethernet-type>
      <type>2048</type>
      </ethernet-type>
      </ethernet-match>
      <ipv4-destination>10.0.10.0/24</ipv4-destination>
      </match>
      <hard-timeout>0</hard-timeout>
      <flags />
      <priority>162</priority>
      <table_id>0</table_id>
      <flow-statistics xmlns="urn:opendaylight:flow:statistics">
      <packet-count>0</packet-count>
      <byte-count>0</byte-count>
      <duration>
      <nanosecond>34000000</nanosecond>
      <second>8</second>
      </duration>
      </flow-statistics>
      <idle-timeout>0</idle-timeout>
      </flow>

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            Avishnoi Anil Vishnoi
            ecelgp Luis Gomez
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: