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

ONOS node stuck in ACTIVE state after being killed and recovered

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.0.0
    • Component/s: None
    • Labels:
    • Story Points:
      3
    • Epic Link:

      Description

      We see this issue in Segment Routing nightly tests. After killing onos-1 and recovering it, sometimes it stays in ACTIVE state.

      It seems to be different than ONOS-7812 which only happens when cluster starting up. And there's also a larger chance to reproduce this issue.

        Attachments

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

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            You You Wang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: