Uploaded image for project: 'controller'
  1. controller
  2. CONTROLLER-872

Flow state not written to node after it is removed and re-added

    XMLWordPrintable

Details

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

    • 2000

    Description

      When flows are written to a node and it offine and returns after a few mins, the flow rules are not written to the node. Even an explicit write does not help.

      Here are the flows written to a node on Table #50 before the node goes offline. When the node returns, these rules are not written to the node. Sometimes I see the flow LOADBALANCER_FORWARD_FLOW1_10.0.0.5 being written. Sometimes I see LOADBALANCER_REVERSE_FLOW_10.0.0.5_10.0.0.8 written. It is not deterministic.

      <table xmlns="urn:opendaylight:flow:inventory">
      <id>50</id>
      <flow>
      <id>LOADBALANCER_REVERSE_FLOW_10.0.0.5_10.0.0.8</id>
      <flow-name>LOADBALANCER_REVERSE_FLOW_10.0.0.5_10.0.0.8</flow-name>
      <match>...</match>
      <priority>32768</priority>
      <idle-timeout>0</idle-timeout>
      <instructions>...</instructions>
      <barrier>true</barrier>
      <table_id>50</table_id>
      <hard-timeout>0</hard-timeout>
      </flow>
      <flow>
      <id>DEFAULT_PIPELINE_FLOW_50</id>
      <flow-name>DEFAULT_PIPELINE_FLOW_50</flow-name>
      <match/>
      <priority>0</priority>
      <idle-timeout>0</idle-timeout>
      <instructions>...</instructions>
      <barrier>true</barrier>
      <table_id>50</table_id>
      <hard-timeout>0</hard-timeout>
      </flow>
      <flow>
      <id>LOADBALANCER_FORWARD_FLOW1_10.0.0.5</id>
      <flow-name>LOADBALANCER_FORWARD_FLOW1_10.0.0.5</flow-name>
      <match>...</match>
      <priority>32768</priority>
      <idle-timeout>0</idle-timeout>
      <instructions>...</instructions>
      <barrier>true</barrier>
      <table_id>50</table_id>
      <hard-timeout>0</hard-timeout>
      </flow>
      <flow>
      <id>LOADBALANCER_REVERSE_FLOW_10.0.0.5_10.0.0.7</id>
      <flow-name>LOADBALANCER_REVERSE_FLOW_10.0.0.5_10.0.0.7</flow-name>
      <match>...</match>
      <priority>32768</priority>
      <idle-timeout>0</idle-timeout>
      <instructions>...</instructions>
      <barrier>true</barrier>
      <table_id>50</table_id>
      <hard-timeout>0</hard-timeout>
      </flow>
      <flow>
      <id>LOADBALANCER_FORWARD_FLOW2_10.0.0.5_10.0.0.8</id>
      <flow-name>LOADBALANCER_FORWARD_FLOW2_10.0.0.5_10.0.0.8</flow-name>
      <match>...</match>
      <priority>32769</priority>
      <idle-timeout>0</idle-timeout>
      <instructions>...</instructions>
      <barrier>true</barrier>
      <table_id>50</table_id>
      <hard-timeout>0</hard-timeout>
      </flow>
      <flow>
      <id>LOADBALANCER_FORWARD_FLOW2_10.0.0.5_10.0.0.7</id>
      <flow-name>LOADBALANCER_FORWARD_FLOW2_10.0.0.5_10.0.0.7</flow-name>
      <match>...</match>
      <priority>32769</priority>
      <idle-timeout>0</idle-timeout>
      <instructions>...</instructions>
      <barrier>true</barrier>
      <table_id>50</table_id>
      <hard-timeout>0</hard-timeout>
      </flow>
      </table>

      Attachments

        1. dummy1.pcap
          35 kB
          Srini Seetharaman
        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            Unassigned Unassigned
            srini.seetharaman@gmail.com Srini Seetharaman
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: