Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
HTML |
---|
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-Fabric/lastSuccessfulBuild/artifact/HAclusterRestart_master_20-builds_graph.jpg", alt="HAclusterRestart", style="width:525px;height:350px;border:0"> |
commit d15c5f63f779ce070e0c4e25020059aef7ff18fe da3b9f09807e4054835495b1d61b3956ef5c5cbd (HEAD -] master, origin/master, origin/HEAD)
Author: Jordan Halterman [jordan@opennetworking.org]
AuthorDate: Wed Fri Oct 3 165 13:0928:24 51 2018 -0700
Commit: Ray Milkey Charles Chan [ray@opennetworkingcharles@opennetworking.org]
CommitDate: Sat Tue Oct 6 039 17:3224:55 35 2018 +0000
[ONOS-7801] Avoid converting local node on every lookup in ClusterStore
Avoid closing DeviceFlowTable when flows are purged on device down event
--
(cherry picked from commit cd4276521ca0a7268353317ede37de33cdbe4c52)
Case 1: Starting up 7 node(s) ONOS cluster - PASS
...
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 5: Setting up and gathering data for current state -
...
FAIL
- 5.1 Check that each switch has a master - PASS
- 5.2 Get the Mastership of each switch from each controller - No Result
- 5.3 Read device roles from ONOS - PASS
- 5.4 Check for consistency in roles from each controller - PASS FAIL
- ONOS nodes have different views of switch roles
- 5.5 Get the intents from each controller - PASS
- 5.6 Check for consistency in Intents from each controller - PASS
- 5.7 Get the flows from each controller - PASS
- 5.8 Check for consistency in Flows from each controller - PASS
- 5.9 Get the OF Table entries - No Result
- 5.10 Start continuous pings - No Result
- 5.11 Collecting topology information from ONOS - No Result
- 5.12 Host view is consistent across ONOS nodes - PASS
- 5.13 Each host has an IP address - PASS
- 5.14 Cluster view is consistent across ONOS nodes - PASS
- 5.15 Cluster view correct across ONOS nodes - PASS
- 5.16 Comparing ONOS topology to MN - PASS
- 5.17 Device information is correct - PASS
- 5.18 Links are correct - PASS
- 5.19 Hosts are correct - PASS
...
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 104: Check connectivity -
...
FAIL
- 104.1 Ping between all hosts - PASS FAIL
- Failed to ping between all hosts
Case 10: Restore a link to ensure that Link Discovery is working properly - PASS
...
- 8.1 Comparing ONOS topology to MN topology - PASS
- 8.2 Hosts view is consistent across all ONOS nodes - PASS
- 8.3 Hosts information is correct - PASS
- 8.4 Host attachment points to the network - PASS
- 8.5 Clusters view is consistent across all ONOS nodes - PASS
- 8.6 There is only one SCC - PASS
- 8.7 Device information is correct - PASS
- 8.8 Links are correct - PASS
- 8.9 Hosts are correct - PASS
- 8.10 Checking ONOS nodes - PASS
Case 104: Check connectivity -
...
FAIL
- 104.1 Ping between all hosts - PASS FAIL
- Failed to ping between all hosts
Case 13: Test Cleanup - PASS
...