Versions Compared

Old Version 652

changes.mady.by.user Jenkins Technical User

Saved on

compared with

New Version 653

changes.mady.by.user Jenkins Technical User

Saved on

Key

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

...

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

commit 03368b3d6a38b15679e960c4c4b61fca366ed3b5 f152f4bb2fcbbc957060b55839707d2f6ad438c2 (HEAD -] master, origin/master, origin/HEAD)
Author: Jian Li [pyguni@gmail.comONOS Jenkins User [jenkins@onlab.us]
AuthorDate: Tue May 26 00:31:27 Jun 2 18:58:58 2020 +09000000
Commit: Jian Li [pyguni@gmail.comONOS Jenkins User [jenkins@onlab.us]
CommitDate: Mon May 25 17:22:46 Tue Jun 2 18:58:58 2020 +0000
Fix: perform exact port match for full port mask value 0xFFFF
--
(cherry picked from commit 22ce467ad0f3de50e7f4848dfda2c0d872f7d711)


Starting snapshot 2.4.0-SNAPSHOT

Case 1: Constructing test variables Case 1: Constructing test variables and building ONOS package - PASS

...

  • 62.1 Deleteing firewall rules - PASS (tick)
  • 62.2 Checking ONOS nodes - 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)
  • 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)FAIL (error)
    • ONOS shows 12 SCCs
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - PASS (tick)FAIL (error)
    • Links are incorrect
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - PASS (tick)

...

  • 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 - FAIL (error)
    • ONOS nodes have different views of switch roles
  • PASS (tick)
  • 7.4 Get the intents from each controller - PASS (tick)
  • 7.5 Check for consistency in Intents from each controller - PASS (tick)
  • 7.6 Compare current intents with intents before the failure - PASS (tick)
  • 7.7 Get the OF Table entries and compare to before component failure - PASS (tick)FAIL (error)
    • Changes were found in the flow tables
  • 7.8 Leadership Election is still functional - PASS (tick)FAIL (error)
    • Something went wrong with Leadership election

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 minute then ping again - 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

...

  • 15.1 Run for election on each node - FAIL (error)
  • At least one node failed to run for leadership
    • Skipping the rest of this case.
  • oldLeader is a candidate, and leader if only 1 node - No Result (warning)

Case 17: Check for basic functionality with distributed primitives - PASS

...

  • 9.1 Kill Link between s28 and s3 - 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 - FAIL (error)
    • ONOS topology don't match Mininet
  • 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 - FAIL (error)
    • ONOS shows 13 12 SCCs
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - FAIL (error)
    • Links are incorrect
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - PASS (tick)

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

...

  • 10.1 Bring link between s28 and s3 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 topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 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 - FAIL (error)
    • ONOS shows 13 12 SCCs
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - FAIL (error)
    • Links are incorrect
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - PASS (tick)

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

...

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 topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 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 - FAIL (error)
    • ONOS shows 14 13 SCCs
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - FAIL (error)
    • Links are incorrect
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - PASS (tick)

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

...

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 topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 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 - FAIL (error)
    • ONOS shows 13 12 SCCs
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - FAIL (error)
    • Links are incorrect
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - PASS (tick)

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

...