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-1.12/1043/

...

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

commit 91dfb74f4ea9a72e0849932620b84d815b7ea774 74b354556ee81ee5896db8fc3fcfd3462a35d722 (HEAD -] onos-1.12, origin/onos-1.12)
Author: Charles Chan [rascov@gmail.com]
AuthorDate: Tue Thu Aug 7 1216 21:4802:36 34 2018 -0700
Commit: Charles Chan [charles@opennetworking.org]
CommitDate: Wed Fri Aug 8 2317 17:1444:29 35 2018 +0000
Move device event handling to another thread in XconnectManager
--
(cherry picked from commit 168111e81cdba245cde4ac94844aa0c561cb0097)
Do not queue VERIFY objectives

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

...

  • 1.1 Constructing test variables - PASS (tick)
  • 1.2 Apply cell to environment - PASS (tick)
  • 1.3 Uninstalling ONOS package - PASS (tick)
  • 1.4 Starting Mininet - PASS (tick)
  • 1.5 Creating ONOS package - PASS (tick)
  • 1.6 Installing ONOS package - PASS (tick)
  • 1.7 Set up ONOS secure SSH - PASS (tick)
  • 1.8 Checking ONOS service - PASS (tick)
  • 1.9 Starting ONOS CLI sessions - PASS (tick)
  • 1.10 Checking ONOS nodes - PASS (tick)
  • 1.11 Checking ONOS applications - PASS (tick)
  • 1.12 Checking ONOS nodes - PASS (tick)
  • 1.13 Activate apps defined in the params file - No Result (warning)
  • 1.12 14 Set ONOS configurations - PASS (tick)
  • 1.13 15 Check app ids - PASS (tick)
  • 1.14 16 Set logging levels - PASS (tick)

...

  • 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

...