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.14/1010/

...

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

commit 4a92c0d0130aab3781a2203782bd42006d9f1acf 1dd9474e104f20292a6dbdc2cfc6e09f8e45c4c8 (HEAD -] onos-1.14, origin/onos-1.14, master)
Author: Charles Chan Jordan Halterman [rascov@gmailjordan@opennetworking.comorg]
AuthorDate: Fri Wed Sep 21 1126 17:2943:12 46 2018 -0700
Commit: Charles Chan Ray Milkey [rascov@gmailray@opennetworking.comorg]
CommitDate: Fri Sep 21 1628 03:0858:32 2018 -0700
Fix serialization issue59 2018 +0000

Append lock timeout to JAVA_OPTS to avoid overwrite
--
(cherry picked from commit 6219399c568cc6f665c2e232a83d2339b61b1bf9)

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 -

...

FAIL

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

...

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

...

FAIL

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

...