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/HAfullNetPartition/230/

...

commit dd50f9a798356434140b2cbff26cce22df1cea41 0cf9e346d693db75136e1069afe348d2272cef68 (HEAD, origin/onos-1.5, onos-1.5)
Author: Jayasree Ghosh Charles Chan [jghosh@partnerrascov@gmail.ciena.com]
AuthorDate: Thu Jun 9 1816 20:0743:19 2016 +0530-0700
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Fri Jun 10 1617 17:5759:38 58 2016 +0000
ONOS-4635:Fix Issue with add flows using flowobjective-forward REST API with incorrect priority

Backport bugfix for NPE to onos-1.5
--
(from commit 04b1fe9adab1382e89a743174b40505f900cd6b9)

Change-Id: Ie2af821e232bc8a1c9d6828c464bf3e54ad8cd11
HTML
<iframe src="https://onos-jenkins.onlab.us/job/HAfullNetPartition/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

  • 61.1 Checking ONOS Logs for errors - No Result (warning)
  • 61.2 Partitioning ONOS nodes - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN topology - FAIL (error)
  • ONOS topology don't match Mininet
  • PASS (tick)
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.6 There is only one SCC - FAIL (error)
  • ONOS shows 2 SCCs
  • PASS (tick)
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - FAIL (error)
  • Links are incorrect
  • PASS (tick)
  • 8.9 Checking ONOS nodes - PASS (tick)

Case 7: Running ONOS Constant State Tests -

...

FAIL

  • 7.1 Check that each switch has a master - PASS (tick)
  • 7.2 Read device roles from ONOS - PASS (tick)
  • 7.3 Check for consistency in roles from each controller - PASS (tick)
  • 7.4 Get the intents and compare across all nodes - PASS (tick)
  • 7.5 Check for consistency in Intents from each controller - PASS (tick)FAIL (error)
    • ONOS nodes have different views of intents
  • 7.6 Compare current intents with intents before the failure - PASS (tick)failure - FAIL (error)
    • The Intents changed during failure
  • 7.7 Get the OF Table entries and compare to before component failure - PASS (tick)FAIL (error)
    • Changes were found in the flow tables
  • 7.8 Leadership Election is still functional - PASS (tick)

...

  • 62.1 Deleteing firewall rules - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology - FAIL

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - FAIL (error)
    • ONOS nodes have different views of clusters
  • 8.6 There is only one SCC - FAIL (error)
    • ONOS shows 10 3 SCCs
  • 8.7 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Checking ONOS nodes - PASS (tick)

Case 7: Running ONOS Constant State Tests - FAIL

  • 7.1 Check that each switch has a master - PASS (tick)
  • 7.2 Read device roles from ONOS - PASS (tick)
  • 7.3 Check for consistency in roles from each controller - PASS (tick)
  • 7.4 Get the intents and compare across all nodes - PASS (tick)
  • 7.5 Check for consistency in Intents from each controller - FAIL (error)
    • ONOS nodes have different views of intents
  • 7.6 Compare current intents with intents before the failure - FAIL (error)
    • The Intents changed during failure
  • 7.7 Get the OF Table entries and compare to before component failure - FAIL (error)
    • Changes were found in the flow tables
  • 7.8 Leadership Election is still functional - PASS (tick)

...

  • 4.1 Ping across added host intents - 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 - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • PASS (tick)

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

...

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

Case 8: Compare ONOS Topology view to Mininet topology - FAIL

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - FAIL (error)
    • ONOS nodes have different views of clusters
  • 8.6 There is only one SCC - FAIL (error)
    • ONOS shows 10 4 SCCs
  • 8.7 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Checking ONOS nodes - PASS (tick)

Case 4: Verify connectivity by sending traffic across Intents -

...

PASS

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.
  • PASS (tick)
  • 4.2 Check Intent 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.
  • PASS (tick)

Case 10: Restore a link to ensure that Link Discovery is working properly - PASS

...

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

Case 8: Compare ONOS Topology view to Mininet topology - FAIL

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - FAIL (error)
    • ONOS nodes have different views of clusters
  • 8.6 There is only one SCC - FAIL (error)
    • ONOS shows 10 3 SCCs
  • 8.7 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Checking ONOS nodes - PASS (tick)

Case 4: Verify connectivity by sending traffic across Intents - PASS

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

...

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 - FAIL

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - FAIL (error)
    • ONOS nodes have different views of clusters
  • 8.6 There is only one SCC - FAIL (error)
    • ONOS shows 10 2 SCCs
  • 8.7 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Checking ONOS nodes - PASS (tick)

Case 4: Verify connectivity by sending traffic across Intents -

...

PASS

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.
  • PASS (tick)
  • 4.2 Check Intent 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.
  • PASS (tick)

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 - FAIL

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - FAIL (error)
    • ONOS nodes have different views of clusters
  • 8.6 There is only one SCC - FAIL (error)
    • ONOS shows 10 3 SCCs
  • 8.7 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Checking ONOS nodes - PASS (tick)

Case 4: Verify connectivity by sending traffic across Intents -

...

PASS

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.
  • PASS (tick)
  • 4.2 Check Intent 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.
  • PASS (tick)

Case 13: Test Cleanup - PASS

...