Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://onos-jenkins.onlab.us/job/HAclusterRestart/398/

...

commit c612054893d8063d8a2eabe6fa0c58b4f2bec7f0 ef2e63998b679c456cbb3f641cec8307263e262b (HEAD, origin/master, origin/HEAD, master)
Author: Phaneendra Manda Bharat saraswal [phaneendrabharat.manda@huaweisaraswal@huawei.com]
AuthorDate: Mon Tue Apr 18 1319 19:5750:16 32 2016 +0530
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Tue Apr 19 0117:4817:19 49 2016 +0000
[ONOS-4226]Service function group class added for sf statistics
YANG augment's generated file name resolver implementation and UT fixes.
HTML
<iframe src="https://onos-jenkins.onlab.us/job/HAclusterRestart/plot/Plot-HA/getPlot?index=2&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 Create cell file - No Result (warning)
  • 1.2 Applying cell variable to environment - No Result (warning)
  • 1.3 Starting Mininet - PASS (tick)
  • 1.4 Git checkout and pull master - No Result (warning)
  • 1.5 Using mvn clean install - PASS (tick)
  • 1.6 Creating ONOS package - PASS (tick)
  • 1.7 Installing ONOS package - PASS (tick)
  • 1.8 Checking if ONOS is up yet - PASS (tick)
  • 1.9 Checking ONOS nodes - PASS (tick)FAIL (error)
    • Nodes check NOT successful
  • 1.10 Activate apps defined in the params file - No Result (warning)
  • 1.11 Set ONOS configurations - PASS (tick)
  • 1.12 App Ids check - PASS (tick)

...

  • 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 Comparing ONOS topology to MN topology - PASS (tick)FAIL (error)
    • ONOS topology don't match Mininet
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)FAIL (error)
    • ONOS nodes have different views of hosts
  • 8.3 Hosts information is correct - PASS (tick)FAIL (error)
    • Host information is incorrect
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - PASS (tick)FAIL (error)
    • ONOS nodes have different views of clusters
  • 8.6 There is only one SCC - PASS (tick)
  • 8.7 Device information is correct - PASS (tick)FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - PASS (tick)FAIL (error)
    • Links are incorrect
  • 8.9 Hosts are correct - PASS (tick)FAIL (error)
    • Hosts are incorrect
  • 8.10 Checking ONOS nodes - PASS (tick)FAIL (error)
    • Nodes check NOT successful

Case 3: Adding host Intents - FAIL

...

  • 3.1 Install reactive forwarding app - PASS (tick)
  • 3.2 Check app ids - PASS (tick)
  • 3.3 Discovering Hosts( Via pingall for now ) - PASS (tick)
  • 3.4 Uninstall reactive forwarding app - PASS (tick)
  • 3.5 Check app ids - PASS (tick)
  • 3.6 Add host intents via cli - PASS (tick)
  • 3.7 Intent Anti-Entropy dispersion - FAIL (error)

Case 8: Compare ONOS Topology view to Mininet topology -

...

FAIL

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN topology - PASS (tick)FAIL (error)
    • ONOS topology don't match Mininet
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)FAIL (error)
    • ONOS nodes have different views of hosts
  • 8.3 Hosts information is correct - PASS (tick)FAIL (error)
    • Host information is incorrect
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - PASS (tick)FAIL (error)
    • ONOS nodes have different views of clusters
  • 8.6 There is only one SCC - PASS (tick)
  • 8.7 Device information is correct - PASS (tick)FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - PASS (tick)FAIL (error)
    • Links are incorrect
  • 8.9 Hosts are correct - PASS (tick)FAIL (error)
    • Hosts are incorrect
  • 8.10 Checking ONOS nodes - PASS (tick)FAIL (error)
    • Nodes check NOT successful

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 5: Setting up and gathering data for current state - No Result

  • 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 - FAIL (error)
    • Error in reading roles from ONOS
  • 5.3 Check for consistency in roles from each controller - FAIL (error)
    • ONOS nodes have different views of switch roles
  • 5.4 Get the intents from each controller - FAIL (error)
    • Error in reading intents from ONOS
  • 5.5 Check for consistency in Intents from each controller - FAIL (error)
    • ONOS nodes have different views of intents
  • 5.6 Get the flows from each controller - FAIL (error)
    • Error in reading flows from ONOS