Uploaded image for project: 'ONOS'
  1. ONOS
  2. ONOS-2433

Intents stuck in FAILED state due to cascading topology changes.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 1.2.0, 1.2.1
    • Fix Version/s: 1.3.0, 1.2.2
    • Component/s: None
    • Labels:
      None
    • Environment:

      Three instances in FSFW with Mininet

      Description

      We start SDN-IP and install some intents. Then we shutdown the FSFW which removes the entire topology, all intents go to FAILED. Then we start up the FSFW which causes the same topology to reconnect to ONOS. Some intents get reinstalled correctly, however some are left in the FAILED state.

      We believe this is due to cascading topology changes of the multiple successive topology events which trying to recalculate the intents.

      Solved by added FAILED intents to the IntentCleanup thread, meaning that intents that have been FAILED for a while get retried.

        Attachments

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

          Activity

            People

            Assignee:
            jono Jonathan Hart
            Reporter:
            jono Jonathan Hart
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: