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

...

commit 404b0fcf3688a8c699b14ad6efe40f5d723b9667 4f7600bc8cefb11bc70558ddfcba4d0b79c8b0c9 (HEAD, origin/master, origin/HEAD, master)
Author: lishuai [lishuai12@huaweiMahesh Poojary Huawei [mahesh.poojary@huawei.com]
AuthorDate: Fri Dec 4 0902:5931:59 55 2015 +08000530
Commit: lishuai Gerrit Code Review [lishuai12@huaweigerrit@onlab.comus]
CommitDate: Fri Sat Dec 4 115 03:0809:51 18 2015 +08000000

[ONOS-3479] Add the implementation of ArpService interface.3162] Test stub on FlowObjectiveService
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>

...

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

Case 3: Adding host Intents -

...

PASS

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 ) - 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)PASS (tick)

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

...

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)
  • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.4 Hosts information is correct - PASS (tick)
  • 8.5 Host attachment points to the network - PASS (tick)
  • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.7 There is only one SCC - PASS (tick)
  • 8.8 Device information is correct - PASS (tick)
  • 8.9 Links are correct - PASS (tick)
  • 8.10 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 ) - 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)FAIL (error)
    • Error looking up host ids
  • 3.7 Intent Anti-Entropy dispersion - PASS (tick)FAIL (error)

Case 7: Running ONOS Constant State Tests - FAIL

...

  • 7.1 Check that each switch has a master - PASS (tick)
  • 7.2 Read device roles from ONOS - PASS (tick)
  • 7.3 Check for consistency in roles from each controller - PASS (tick)
  • 7.4 Get the intents and compare across all nodes - PASS (tick)
  • 7.5 Check for consistency in Intents from each controller - PASS (tick)FAIL (error)
    • ONOS nodes have different views of intents
  • 7.6 Get the OF Table entries and compare to before component failure - FAIL (error)
    • Changes were found in the flow tables
  • 7.7 Leadership Election is still functional - 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 - PASS (tick)FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • 4.2 Check Intent state - PASS (tick)
  • 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 15: Check that Leadership Election is still functional - PASS

...

  • 15.1 Run for election on each node - PASS (tick)
  • 15.2 Check that each node shows the same leader and candidates - PASS (tick)
  • 15.3 Find current leader and withdraw - PASS (tick)
  • 15.4 Check that a new node was elected leader - PASS (tick)
  • 15.5 Check that that new leader was the candidate of old leader - PASS (tick)
  • 15.6 Run for election on old leader( just so everyone is in the hat ) - PASS (tick)
  • 15.7 Check that oldLeader is a candidate, and leader if only 1 node - PASS (tick)

Case 17: Check for basic functionality with distributed primitives -

...

FAIL

Test the methods of the distributed primitives (counters and sets) throught the cli

  • 17.1 Increment then get a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • PASS (tick)
  • 17.2 Get then Increment a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.3 Counters we added have the correct values - FAIL (error)
  • Added counters are incorrect
  • PASS (tick)
  • 17.4 Add -8 to then get a default counter on each node - FAIL (error)
  • Error incrementing default counter
  • PASS (tick)
  • 17.5 Add 5 to then get a default counter on each node - PASS (tick)
  • 17.6 Get then add 5 to a default counter on each node - PASS (tick)
  • 17.7 Counters we added have the correct values - PASS (tick)
  • 17.8 Increment and get an in-memory counter on each node - PASS (tick)
  • 17.9 Get then Increment a in-memory counter on each node - PASS (tick)
  • 17.10 Counters we added have the correct values - PASS (tick)
  • 17.11 Add -8 Add 5 to then get a default in-memory counter on each node - FAIL (error)
  • Error incrementing default counter
  • PASS (tick)
  • 17.12 Add 5 to then get a in-memory counter on each node - PASS (tick)
  • 17.6 13 Get then add 5 to a default counter on each node - FAIL (error)
  • Error incrementing default counter
  • in-memory counter on each node - PASS (tick)
  • 17.14 Counters we added have the correct values - PASS (tick)
  • 17.15 Check counters are consistant across nodes - PASS (tick)
  • 17.16 Counters we added have the correct values - PASS (tick)
  • 17.17 Distributed Set get - PASS (tick)
  • 17.18 Distributed Set size - PASS (tick)
  • 17.19 Distributed Set add() - PASS (tick)
  • 17.20 Distributed Set addAll() - PASS (tick)
  • 17.21 Distributed Set contains() - PASS (tick)
  • 17.22 Distributed Set containsAll() - PASS (tick)
  • 17.23 Distributed Set remove() - PASS (tick)
  • 17.24 Distributed Set removeAll() - PASS (tick)
  • 17.25 Distributed Set addAll() - PASS (tick)
  • 17.26 Distributed Set clear() - PASS (tick)
  • 17.27 Distributed Set addAll() - PASS (tick)
  • 17.28 Distributed Set retain() - PASS (tick)
  • 17.29 Partitioned Transactional maps put - PASS (tick)
  • 17.30 Partitioned Transactional maps get - PASS (tick)
  • 17.31 In-memory Transactional maps put - PASS (tick)
  • 17.32 In-Memory Transactional maps get - PASS (tick)

Case 9: Turn off a link to ensure that Link Discovery is working properly - PASS

  • 9.1 Kill Link between s3 and s28 - 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 - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)
  • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.4 Hosts information is correct - PASS (tick)
  • 8.5 Host attachment points to the network - PASS (tick)
  • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.7 There is only one SCC - FAIL (error)
    • ONOS shows 4 SCCs
  • 8.8 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.9 Links are correct - FAIL (error)
    • Links are incorrect
  • 8.10 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 - PASS (tick)
  • 4.4 Wait a minute then ping again - FAIL (error)
    • Intents have not been installed correctly, pings failed.

Case 10: Restore a link to ensure that Link Discovery is working properly - PASS

  • 10.1 Bring link between s3 and s28 back up - 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 - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)
  • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.4 Hosts information is correct - PASS (tick)
  • 8.5 Host attachment points to the network - PASS (tick)
  • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.7 There is only one SCC - FAIL (error)
    • ONOS shows 3 SCCs
  • 8.8 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.9 Links are correct - FAIL (error)
    • Links are incorrect
  • 8.10 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 - PASS (tick)
  • 4.4 Wait a minute then ping again - FAIL (error)
    • Intents have not been installed correctly, pings failed.

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

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)
  • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.4 Hosts information is correct - PASS (tick)
  • 8.5 Host attachment points to the network - PASS (tick)
  • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.7 There is only one SCC - FAIL (error)
    • ONOS shows 4 SCCs
  • 8.8 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.9 Links are correct - FAIL (error)
    • Links are incorrect
  • 8.10 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 - FAIL (error)
    • Intents are not all in INSTALLED state
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - FAIL (error)
    • Intents have not been installed correctly, pings failed.

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

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - PASS (tick)
  • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.4 Hosts information is correct - PASS (tick)
  • 8.5 Host attachment points to the network - PASS (tick)
  • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.7 There is only one SCC - FAIL (error)
    • ONOS shows 3 SCCs
  • 8.8 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.9 Links are correct - FAIL (error)
    • Links are incorrect
  • 8.10 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 - PASS (tick)
  • 4.4 Wait a minute then ping again - FAIL (error)
    • Intents have not been installed correctly, pings failed.

Case 13: Test Cleanup - PASS

  • 13.1 Killing tcpdumps - No Result (warning)
  • 13.2 Stopping Mininet - PASS (tick)
  • 13.3 Checking ONOS Logs for errors - No Result (warning)