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

...

...

HTML

<iframe src="https://onos-jenkins.onlab.us/job/HAClusterRestart/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

Case 1: Setting up test environment - FAIL

Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.

  • 1.1 Applying cell variable to environment - No Result (warning)
  • 1.2 Starting Mininet - PASS (tick)
  • 1.3 Git checkout and pull master - No Result (warning)
  • 1.4 Using mvn clean install - PASS (tick)
  • 1.5 Creating ONOS package - PASS (tick)
  • 1.6 Installing ONOS package - PASS (tick)
  • 1.7 Checking if ONOS is up yet - PASS (tick)
  • 1.8 App Ids check - FAIL (error)
    • Something is wrong with app Ids

Case 2: Assigning devices to controllers - PASS

Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device.

  • 2.1 Assign switches to controllers - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology - FAIL

Compare topology objects between Mininet and ONOS

  • 8.1 Create TestONTopology object - PASS (tick)
  • 8.2 Comparing ONOS topology to MN - No Result (warning)
  • 8.3 Collecting topology information from ONOS - PASS (tick)
  • 8.4 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.5 Hosts information is correct - PASS (tick)
  • 8.6 Host attachment points to the network - PASS (tick)
  • 8.7 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.8 There is only one SCC - FAIL (error)
    • ONOS shows 28 SCCs
  • 8.9 Device information is correct - PASS (tick)
  • 8.10 Port information is correct - FAIL (error)
    • Port information is incorrect
  • 8.11 Links are correct - FAIL (error)
    • Links are incorrect
  • 8.12 Checking ONOS nodes - PASS (tick)

Case 3: Adding host Intents - FAIL

Discover hosts by using pingall then assign predetermined host-to-host intents. After installation, check that the intent is distributed to all nodes and the state is INSTALLED

  • 3.1 Install reactive forwarding app - PASS (tick)
  • 3.2 Check app ids - PASS (tick)
  • 3.3 Discovering Hosts( Via pingall for now ) - FAIL (error)
    • Reactive Pingall failed, one or more ping pairs failed
  • 3.4 Uninstall reactive forwarding app - PASS (tick)
  • 3.5 Check app ids - PASS (tick)
  • 3.6 Add host intents via cli - FAIL (error)
    • Error looking up host ids
  • 3.7 Intent Anti-Entropy dispersion - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology - FAIL

Compare topology objects between Mininet and ONOS

  • 8.1 Create TestONTopology object - PASS (tick)
  • 8.2 Comparing ONOS topology to MN - No Result (warning)
  • 8.3 Collecting topology information from ONOS - PASS (tick)
  • 8.4 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.5 Hosts information is correct - PASS (tick)
  • 8.6 Host attachment points to the network - PASS (tick)
  • 8.7 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.8 There is only one SCC - FAIL (error)
    • ONOS shows 28 SCCs
  • 8.9 Device information is correct - PASS (tick)
  • 8.10 Port information is correct - FAIL (error)
    • Port information is incorrect
  • 8.11 Links are correct - FAIL (error)
    • Links are incorrect
  • 8.12 Checking ONOS nodes - PASS (tick)

Case 4: Verify connectivity by sendind traffic across Intents - FAIL

Ping across added host intents to check functionality and check the state of the intent

  • 4.1 Ping across added host intents - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - FAIL (error)
    • Some topics were lost
  • 4.4 Wait a minute then ping again - FAIL (error)
    • Intents have not been installed correctly, pings failed.

Case 5: Setting up and gathering data for current state - FAIL

  • 5.1 Check that each switch has a master - FAIL (error)
    • Some devices don't have a master assigned
  • 5.2 Get the Mastership of each switch from each controller - PASS (tick)
  • 5.3 Check for consistency in roles from each controller - PASS (tick)
  • 5.4 Get the intents from each controller - PASS (tick)
  • 5.5 Check for consistency in Intents from each controller - PASS (tick)
  • 5.6 Get the flows from each controller - PASS (tick)
  • 5.7 Check for consistency in Flows from each controller - PASS (tick)
  • 5.8 Get the OF Table entries - No Result (warning)
  • 5.9 Start continuous pings - No Result (warning)
  • 5.10 Create TestONTopology object - No Result (warning)
  • 5.11 Collecting topology information from ONOS - No Result (warning)
  • 5.12 Host view is consistent across ONOS nodes - PASS (tick)
  • 5.13 Each host has an IP address - PASS (tick)
  • 5.14 Cluster view is consistent across ONOS nodes - PASS (tick)
  • 5.15 Cluster view correct across ONOS nodes - FAIL (error)
    • ONOS shows 28 SCCs
  • 5.16 Comparing ONOS topology to MN - FAIL (error)
    • Topology Check Test NOT successful

Case 14: Start Leadership Election app - PASS

  • 14.1 Install leadership election app - PASS (tick)
  • 14.2 Run for election on each node - PASS (tick)
  • 14.3 Check that each node shows the same leader - PASS (tick)

Case 16: Install Primitives app - PASS

  • 16.1 Install Primitives app - PASS (tick)

Case 17: Check for basic functionality with distributed primitives - No Result

  • 17.1 Increment and get a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.2 Increment and get an in memory counter on each node - PASS (tick)
  • 17.3 Check counters are consistant across nodes - FAIL (error)
    • ONOS Counters are inconsistent across nodes