...
HTML |
---|
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/HAsingleInstanceRestart_onos-1.14_20-builds_graph.jpg", alt="HAsingleInstanceRestart", style="width:525px;height:350px;border:0"> |
commit 7f8bdf83aec35e523618bcd249f855b9303f8eac dcac7b40db1e0ecc6c61035513a86e5f3861470d (HEAD -] onos-1.14, origin/onos-1.14)
Author: Daniel Park [dan.mcpark84@gmail.comONOS Jenkins User [jenkins@onlab.us]
AuthorDate: Fri Wed Aug 24 2229 19:3337:29 12 2018 +09000000
Commit: Jian Li [pyguni@gmail.comONOS Jenkins User [jenkins@onlab.us]
CommitDate: Wed Aug 29 0419:5637:32 12 2018 +0000
Supports a creation of dpdk tunnel bridge and ports in OpenstackNode.
--
(cherry picked from commit e2658baf17d999dab362aecf703cd940659065d2)
Starting snapshot 1.14.0-SNAPSHOT
Case 1: Constructing test variables and building ONOS package - FAIL
...
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Checking ONOS nodes - PASS
Case 3: Adding host
...
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
- 3.2 Check app ids - PASS
- 3.3 Discovering Hosts( Via pingall for now ) - PASS
- 3.4 Uninstall reactive forwarding app - PASS
- 3.5 Check app ids - PASS
- 3.6 Add host intents via cli - PASS
- 3.7 Intent Anti-Entropy dispersion - PASS
Case 7: Running ONOS Constant State Tests - PASS
- 7.1 Check that each switch has a master - PASS
- 7.2 Read device roles from ONOS - PASS
- 7.3 Check for consistency in roles from each controller - PASS
- 7.4 Compare switch roles from before failure - PASS
- 7.5 Get the intents from each controller - PASS
- 7.6 Check for consistency in Intents from each controller - PASS
...
Intents
...
Ping across added host intents to check functionality and check the state of the intent
- 4.1 Check Intent state - PASS
- 4.2 Ping across added host intents - PASS
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS
Case 15: Check that Leadership Election is still functional - PASS
- 15.1 Run for election on each node - PASS
- 15.2 Check that each node shows the same leader and candidates - PASS
- 15.3 Find current leader and withdraw - PASS
- 15.4 Check that a new node was elected leader - PASS
- 15.5 Check that that new leader was the candidate of old leader - PASS
- 15.6 Run for election on old leader( just so everyone is in the hat ) - PASS
- 15.7 Check that oldLeader is a candidate, and leader if only 1 node - No Result
Case 17: Check for basic functionality with distributed primitives - FAIL
Test the methods of the distributed primitives (counters and sets) throught the cli
...
-
...
FAIL
...
- Error getting atomic Value None, found: ['baz']
...
- Error getting atomic Value None, found: ['baz']
...
- Work Queue stats incorrect
...
- Work Queue stats incorrect
...
- Work Queue stats incorrect
...
- Work Queue stats incorrect
...
- Work Queue stats incorrect
Case 9: Turn off a link to ensure that Link Discovery is working properly - PASS
- 9.1 Kill Link between s28 and s3 - PASS
Case 8: Compare ONOS Topology view to Mininet topology - PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Checking ONOS nodes - PASS
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
- 4.2 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- 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 s28 and s3 back up - PASS
Case 8: Compare ONOS Topology view to Mininet topology - PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Checking ONOS nodes - PASS
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
- 4.2 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- 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
Case 8: Compare ONOS Topology view to Mininet topology - PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Checking ONOS nodes - PASS
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
- 4.2 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- 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
Case 8: Compare ONOS Topology view to Mininet topology - PASS
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Checking ONOS nodes - PASS
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
- 4.2 Ping across added host intents - FAIL
- Intents have not been installed correctly, pings failed.
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - FAIL
- Intents have not been installed correctly, pings failed.
Case 13: Test Cleanup - PASS
...