Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

commit 924f01f31f8302a8680a6a16f1e43d56e469bd4f 31551b0c9116e3ff7507bd0f44c9d2220a753241 (HEAD -] master, origin/master, origin/HEAD)
Author: Anurag Chadha Charles Chan [anuragcharles@opennetworking.chadha@hsc.comorg]
AuthorDate: Fri Dec 4 19:48:56 2020 +0530Tue Jan 5 02:00:28 2021 +0000
Commit: Thomas Vachuska pierventre [tom@opennetworkingpier@opennetworking.org]
CommitDate: Fri Wed Jan 8 0013 16:5452:25 16 2021 +0000
[ONOS-8129] Bug fixed for duplicate events when netconf device goes down along with some fixes for NPE in NetconfControllerImpl0100

Lower LLDP log message when an unknown source is found

Case 1: Bridging and Routing Link Failure test with 2x2 Leaf-spine and 1 Onos - PASS

...

  • 2.1 Apply cell to environment - PASS (tick)
  • 2.2 Uninstalling Atomix - PASS (tick)
  • 2.3 Uninstalling ONOS package - PASS (tick)
  • 2.4 Building ONOS Docker image - PASS (tick)
  • 2.5 Create Cluster Config - PASS (tick)
  • 2.6 Installing Atomix via docker containers - PASS (tick)
  • 2.7 Installing ONOS via docker containers - PASS (tick)
  • 2.8 Set up ONOS secure SSH - PASS (tick)
  • 2.9 Starting ONOS CLI sessions - PASS (tick)
  • 2.10 Checking ONOS nodes - PASS (tick)
  • 2.11 Checking ONOS applications - PASS (tick)
  • 2.12 Set logging levels - PASS (tick)
  • 2.13 Set ONOS configurations - PASS (tick)
  • 2.14 Starting Mininet Topology - PASS (tick)
  • 2.15 Configure switches in ONOS - PASS (tick)
  • 2.16 Check number of topology elements - FAIL (error)
    • Unexpected number of links, switches, and/or controllers: The number of links, switches, nodes, and SCCs does not match what was expected
    • ONOS sees 8 devices (8 expected) and 24 links (32 expected) and 1 controllers (1 expected) and 3 SCCs (1 expected)
  • 2.17 Check whether the flow count is >= 350 - PASS (tick)
  • 2.18 Check whether all flow status are ADDED - PASS (tick)
  • 2.19 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE2 - PASS (tick)FAIL (error)
    • IP connectivity failed
  • 2.20 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2 - PASS (tick)
  • 2.21 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2 - PASS (tick)
  • 2.22 Kill link between spine101 and leaf2 - PASS (tick)
  • 2.23 Checking topology after link down - FAIL (error)
    • Topology after link down is incorrect
  • 2.24 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE2_Failure - PASS (tick)
  • 2.25 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2_Failure - PASS (tick)
  • 2.26 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2_Failure - PASS (tick)
  • 2.27 Restore link between spine101 and leaf2 - FAIL (error)
    • Failed to bring link up
  • 2.28 Check whether the flow count is >= 350 - PASS (tick)
  • 2.29 Check whether all flow status are ADDED - PASS (tick)
  • 2.30 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE2_Recovery - PASS (tick)
  • 2.31 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE2_Recovery - PASS (tick)
  • 2.32 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE2_Recovery - PASS (tick)
  • 2.33 Check number of topology elements - FAIL (error)
    • Unexpected number of links, switches, and/or controllers: The number of links, switches, nodes, and SCCs does not match what was expected
    • ONOS sees 8 devices (8 expected) and 24 links (32 expected) and 1 controllers (1 expected) and 3 SCCs (1 expected)
  • 2.34 Stopping Mininet - PASS (tick)
  • 2.35 Copying karaf logs - PASS (tick)

Case 4: Bridging and Routing Link Failure test with 2x2 Leaf-spine and 3 Onos - PASS

  • 4.1 Apply cell to environment - PASS (tick)
  • 4.2 Uninstalling Atomix - PASS (tick)
  • 4.3 Uninstalling ONOS package - PASS (tick)
  • 4.4 Building ONOS Docker image - PASS (tick)
  • 4.5 Create Cluster Config - PASS (tick)
  • 4.6 Installing Atomix via docker containers - PASS (tick)
  • 4.7 Installing ONOS via docker containers - PASS (tick)
  • 4.8 Set up ONOS secure SSH - PASS (tick)
  • 4.9 Starting ONOS CLI sessions - PASS (tick)
  • 4.10 Checking ONOS nodes - PASS (tick)
  • 4.11 Checking ONOS applications - PASS (tick)
  • 4.12 Set logging levels - PASS (tick)
  • 4.13 Set ONOS configurations - PASS (tick)
  • 4.14 Starting Mininet Topology - PASS (tick)
  • 4.15 Configure switches in ONOS - PASS (tick)
  • 4.16 Check number of topology elements - PASS (tick)
  • 4.17 Check whether the flow count is >= 116 - PASS (tick)
  • 4.18 Check whether all flow status are ADDED - PASS (tick)
  • 4.19 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE3 - PASS (tick)
  • 4.20 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE3 - PASS (tick)
  • 4.21 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE3 - PASS (tick)
  • 4.22 Kill link between spine101 and leaf2 - PASS (tick)
  • 4.23 Checking topology after link down - PASS (tick)
  • 4.24 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE3_Failure - PASS (tick)
  • 4.25 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE3_Failure - PASS (tick)
  • 4.26 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE3_Failure - PASS (tick)
  • 4.27 Restore link between spine101 and leaf2 - PASS (tick)
  • 4.28 Check whether the flow count is >= 116 - PASS (tick)
  • 4.29 Check whether all flow status are ADDED - PASS (tick)
  • 4.30 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE3_Recovery - PASS (tick)
  • 4.31 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE3_Recovery - PASS (tick)
  • 4.32 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE3_Recovery - PASS (tick)
  • 4.33 Check number of topology elements - PASS (tick)
  • 4.34 Stopping Mininet - PASS (tick)
  • 4.35 Copying karaf logs - PASS (tick)

Case 5: Bridging and Routing Link Failure test with 4x4 Leaf-spine and 3 Onos - FAIL

  • 5.1 Apply cell to environment - PASS (tick)
  • 5.2 Uninstalling Atomix - PASS (tick)
  • 5.3 Uninstalling ONOS package - PASS (tick)
  • 5.4 Building ONOS Docker image - PASS (tick)
  • 5.5 Create Cluster Config - PASS (tick)
  • 5.6 Installing Atomix via docker containers - PASS (tick)
  • 5.7 Installing ONOS via docker containers - PASS (tick)
  • 5.8 Set up ONOS secure SSH - PASS (tick)
  • 5.9 Starting ONOS CLI sessions - PASS (tick)
  • 5.10 Checking ONOS nodes - PASS (tick)
  • 5.11 Checking ONOS applications - PASS (tick)
  • 5.12 Set logging levels - PASS (tick)
  • 5.13 Set ONOS configurations - PASS (tick)
  • 5.14 Starting Mininet Topology - PASS (tick)
  • 5.15 Configure switches in ONOS - PASS (tick)
  • 5.16 Check number of topology elements - FAIL (error)
    • Unexpected number of links, switches, and/or controllers: The number of links, switches, nodes, and SCCs does not match what was expected
    • ONOS sees 8 devices (8 expected) and 8 links (32 expected) and 3 controllers (3 expected) and 8 SCCs (1 expected)
  • 5.17 Check whether the flow count is >= 350 - PASS (tick)
  • 5.18 Check whether all flow status are ADDED - PASS (tick)
  • 5.19 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE4 - FAIL (error)
    • IP connectivity failed
  • 5.20 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE4 - PASS (tick)
  • 5.21 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE4 - PASS (tick)
  • 5.22 Kill link between spine101 and leaf2 - PASS (tick)
  • 5.23 Checking topology after link down - FAIL (error)
    • Topology after link down is incorrect
  • 5.24 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE4_Failure - FAIL (error)
    • IP connectivity failed
  • 5.25 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE4_Failure - PASS (tick)
  • 5.26 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE4_Failure - PASS (tick)
  • 5.27 Restore link between spine101 and leaf2 - FAIL (error)
    • Failed to bring link up
  • 5.28 Check whether the flow count is >= 350 - PASS (tick)
  • 5.29 Check whether all flow status are ADDED - PASS (tick)
  • 5.30 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4', u'h5', u'h6', u'h7', u'h8'] with tag CASE4_Recovery - FAIL (error)
    • IP connectivity failed
  • 5.31 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE4_Recovery - PASS (tick)
  • 5.32 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE4_Recovery - PASS (tick)
  • 5.33 Check number of topology elements - FAIL (error)
    • Unexpected number of links, switches, and/or controllers: The number of links, switches, nodes, and SCCs does not match what was expected
    • ONOS sees 8 devices (8 expected) and 8 links (32 expected) and 3 controllers (3 expected) and 8 SCCs (1 expected)
  • 5.34 Stopping Mininet - PASS (tick)
  • 5.35 Copying karaf logs - PASS (tick)