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/1378/

...

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 a4dc3c12bc709cce1773e3378c1ce80a7115d912 368bd3d646941ea03458e2e7a56b07021e9df523 (HEAD -] master, origin/master, origin/HEAD)
Author: Carmelo Cascone Jordan Halterman [carmelo@opennetworkingjordan@opennetworking.org]
AuthorDate: Tue Feb Fri Jan 4 12 17:3045:00 57 2019 -0800
Commit: Carmelo Cascone [carmelo@opennetworking.org]
CommitDate: Thu Tue Feb 21 26 23:2403:26 16 2019 +0000
Update install-p4-tools.sh to use P4Runtime v1.0
Ensure devices are marked online during mastership check
--
(cherry picked from commit 8ac0247267b705340f4110b5853d2fbac6a010d6)

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

...

  • 6.1 Backup ONOS data - PASS (tick)
  • 6.2 Checking ONOS Logs for errors - No Result (warning)
  • 6.3 Uninstalling ONOS package - PASS (tick)
  • 6.4 Installing ONOS package - PASS (tick)
  • 6.5 Restore ONOS data - PASS (tick)
  • 6.6 Restart ONOS nodes - No Result (warning)
  • 6.7 Set up ONOS secure SSH - PASS (tick)
  • 6.8 Checking ONOS service - PASS (tick)
  • 6.9 Starting ONOS CLI sessions - FAIL (error)
    • Failed to rerun for election

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 - 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 - FAIL (error)
  • Nodes check NOT successful
  • PASS (tick)

Case 3: Adding host Intents - PASS

...

  • 9.1 Kill Link between s28 and s3 - 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 - 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 - FAIL (error)
    • Nodes check NOT successful
  • PASS (tick)

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

...

  • 10.1 Bring link between s28 and s3 back up - 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 - 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 - FAIL (error)
  • Nodes check NOT successful
  • PASS (tick)

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

...

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 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 - FAIL (error)
    • Nodes check NOT successful
  • PASS (tick)

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

...

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 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 - FAIL (error)
  • Nodes check NOT successful
  • PASS (tick)

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

...