Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://jenkins.onosproject.org/job/HA-pipeline-master/1191/

...

HTML
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/HAbackupRecover_master_20-builds_graph.jpg", alt="HAbackupRecover", style="width:525px;height:350px;border:0">

commit f78e174ca0ac86b0c9fd6d15a81ffdddd996af4f 6f0171362126864449cbd4eafc7cbf17635e02a0 (HEAD -] master, origin/master, origin/HEAD)
Author: Yi Tseng [yi@opennetworking.orgPatryk Konopka [p.konopka2@samsung.com]
AuthorDate: Sun Apr 8 19:57:17 2018 +0800Tue Nov 21 10:44:25 2017 +0100
Commit: Yi Tseng Thomas Vachuska [a86487817@gmailtom@opennetworking.comorg]
CommitDate: Wed Thu Apr 11 0612 21:0756:22 20 2018 +0000

[ONOS-75987239] Fix P4 fabric pipeliner performance issue- ModArp*Instruction not serialized in KryoNamespaces

Case 1: Starting up 7 node(s) ONOS cluster - PASS

...

  • 8.1 Comparing ONOS topology to MN topology - 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 - PASS (tick)
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 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 Check Intent state - PASS (tick)
  • 4.2 Ping across added host intents - FAIL (error)
  • Intents have not been installed correctly, pings failed.
  • 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

...

  • 8.1 Comparing ONOS topology to MN topology - 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 - PASS (tick)
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 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 Check Intent state - PASS (tick)
  • 4.2 Ping across added host intents - FAIL (error)
  • Intents have not been installed correctly, pings failed.
  • 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 11: Killing a switch to ensure it is discovered correctly - PASS

...

  • 8.1 Comparing ONOS topology to MN topology - 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 - PASS (tick)
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 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 Check Intent state - PASS (tick)
  • 4.2 Ping across added host intents - FAIL (error)
  • Intents have not been installed correctly, pings failed.
  • 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

...

  • 8.1 Comparing ONOS topology to MN topology - 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 - PASS (tick)
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 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 Check Intent state - PASS (tick)
  • 4.2 Ping across added host intents - FAIL (error)
  • Intents have not been installed correctly, pings failed.
  • 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

...