Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://onos-jenkins.onlab.us/job/HASingleInstanceRestart/131/

...

  • 6.1 Killing ONOS processes - PASS (tick)
  • 6.2 Checking if ONOS is up yet - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

  • 8.1 Create TestONTopology object - PASS (tick)
  • 8.2 Comparing ONOS topology to MN - No Result (warning)
  • 8.3 Collecting topology information from ONOS - FAIL (error)
  • Topology Check Test NOT successful
  • PASS (tick)

Case 3: Adding host Intents - PASS

...

  • 7.1 Check that each switch has a master - PASS (tick)
  • 7.2 Check if switch roles are consistent across all nodes - PASS (tick)
  • 7.3 Compare switch roles from before failure - PASS (tick)
  • 7.4 Get the intents and compare across all nodes - PASS (tick)
  • 7.5 Get the OF Table entries and compare to before component failure - FAIL (error)
    • Changes were found in the flow tables
  • 7.6 Leadership Election is still functional - PASS (tick)

Case 4: Verify connectivity by sendind traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

  • 4.1 Ping across added host intents - PASS (tick)FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - PASS (tick)FAIL (error)
    • Intents have not been installed correctly, pings failed.

Case 15: Check that Leadership Election is still functional - PASS

...

  • 9.1 Kill Link between s3 and s28 - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

  • 8.1 Create TestONTopology object - PASS (tick)
  • 8.2 Comparing ONOS topology to MN - No Result (warning)
  • 8.3 Collecting topology information from ONOS - FAIL (error)
    • Topology Check Test NOT successful
  • PASS (tick)

Case 4: Verify connectivity by sendind traffic across Intents - FAIL

Ping across added host intents to check functionality and check the state of the intent

  • 4.1 Ping across added host intents - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • 4.2 Check Intent state - FAIL (error)
    • Intents are not all in INSTALLED state
  • PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - FAIL (error)
    • Intents have not been installed correctly, pings failed.

...

  • 10.1 Bring link between s3 and s28 back up - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

  • 8.1 Create TestONTopology object - PASS (tick)
  • 8.2 Comparing ONOS topology to MN - No Result (warning)
  • 8.3 Collecting topology information from ONOS - FAIL (error)
    • Topology Check Test NOT successful
  • PASS (tick)

Case 4: Verify connectivity by sendind traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

  • 4.1 Ping across added host intents - PASS (tick)FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - PASS (tick)FAIL (error)
    • Intents have not been installed correctly, pings failed.

Case 11: Killing a switch to ensure it is discovered correctly - PASS

  • 11.1 Kill s5 - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

  • 8.1 Create TestONTopology object - PASS (tick)
  • 8.2 Comparing ONOS topology to MN - No Result (warning)
  • 8.3 Collecting topology information from ONOS - FAIL (error)
  • Topology Check Test NOT successful
  • PASS (tick)

Case 4: Verify connectivity by sendind traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

  • 4.1 Ping across added host intents - PASS (tick)FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - PASS (tick)FAIL (error)
    • Intents have not been installed correctly, pings failed.

Case 12: Adding a switch to ensure it is discovered correctly - PASS

  • 12.1 Add back s5 - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

  • 8.1 Create TestONTopology object - PASS (tick)
  • 8.2 Comparing ONOS topology to MN - No Result (warning)
  • 8.3 Collecting topology information from ONOS - FAIL (error)
    • Topology Check Test NOT successful
  • PASS (tick)

Case 4: Verify connectivity by sendind traffic across Intents -

...

FAIL

Ping across added host intents to check functionality and check the state of the intent

  • 4.1 Ping across added host intents - PASS (tick)FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - PASS (tick)FAIL (error)
    • Intents have not been installed correctly, pings failed.

Case 13: Test Cleanup - PASS

...