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

Host intents have no flows after some ONOS nodes restart

    XMLWordPrintable

    Details

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

      commit 3ee7200ba5d03e0127333c10575eacad03cfd339

      ONOS_FEATURES=webconsole,onos-api,onos-core,onos-cli,onos-openflow,onos-app-mobility,onos-app-tvue,onos-app-proxyarp, onos-gui

    • Epic Link:
    • Sprint:
      Cardinal Sprint 4 (5/4-5/15), Cardinal Sprint 5 (5/18-5/22)

      Description

      3 of 7 ONOS nodes restart(waiting 10 seconds in between restarts for HZ replication and restarting via onos-kill)

      Afterwards I see intents are still in the Installed state but the flow count is 0. All switches that were primarily assigned to ONOS1-3 switched over to one of the non-restarting nodes.

      I had a continuous ping running across all 10 of my intents and they seem to stop around 30 seconds after I kill ONOS1. The intents were all fed into ONOS1 initially.

      The hosts were discovered via installing the fwd app, pingall then uninstalling the fwd app.

      This may or may not be related to ONOS-436.

        Attachments

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

          Activity

            People

            Assignee:
            jhall Jon Hall
            Reporter:
            jhall Jon Hall
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: