...
commit 879ed7c6ae0189ff24090cce4609a39d7b43da33 1937bbb6f6f7d77b28e8bdb0c3693647a4cd6892 (HEAD, origin/master, origin/HEAD, master)
Author: Madan Jampani Damian ONeill [madan@onlabdoneill@btisystems.uscom]
AuthorDate: Thu Wed Jul 23 208 17:3303:08 19 2015 -0700+0100
Commit: Madan Jampani [madan@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Jul 23 9 20:3331:08 04 2015 -0700
Disable the new change notification support as it seems to have caused a regression+0000
added some null checks for device instance
HTML |
---|
<iframe src="https://onos-jenkins.onlab.us/job/HAsingleInstanceRestartHASingleInstanceRestart/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe> |
...
Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.
- 1.1 Create cell file - No Result 1 .2 Applying cell variable to environment - No Result
- 1.3 2 Starting Mininet - PASS
- 1.4 3 Git checkout and pull master - No Result
- 1.5 4 Using mvn clean install - PASS
- 1.6 5 Creating ONOS package - PASS
- 1.7 6 Installing ONOS package - PASS
- 1.8 7 Checking if ONOS is up yet - PASS
- 1.9 8 App Ids check - PASS
Case 2: Assigning devices to controllers - PASS
...
- 2.1 Assign switches to controllers - PASS
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
- 8.2 Collecting topology information from ONOS - PASS FAIL
- Topology Check Test NOT successful
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
- 3.2 Check app ids - PASS
- 3.3 Discovering Hosts( Via pingall for now ) - PASS FAIL
- Reactive Pingall failed, one or more ping pairs failed
- 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 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 FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS FAIL
- Intents have not been installed correctly, pings failed.
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 - No Result
- 5.3 Get the intents from each controller - No Result
- 5.4 Get the flows from each controller - No Result
- 5.5 Get the OF Table entries - No Result
- 5.6 Collecting topology information from ONOS - No Result
- 5.7 Each host has an IP address - PASS
- 5.8 There is only one dataplane cluster - PASS FAIL
- ONOS shows 11 SCCs
- 5.9 Comparing ONOS topology to MN - PASS
- 5.10 Device information is correct - PASS FAIL
- Device information is incorrect
- 5.11 Links are correct - PASS FAIL
- Links are incorrect
- 5.12 Hosts are correct - PASS
...
Test the methods of the distributed primitives (counters and sets) throught the cli
- 17.1 Increment then and get a default counter on each node - PASS
- 17.2 Get then Increment a default counter on each node - PASS
- 17.3 Counters we added have the correct values - PASS
- 17.4 Add -8 to then get a default counter on each node - PASS
- 17.5 Add 5 to then get a default counter on each node - PASS
- 17.6 Get then add 5 to a default counter on each node - PASS
- 17.7 Counters we added have the correct values - PASS
- 17.8 Increment and get an in - memory counter on each node - PASS
- 17.9 Get then Increment a in-memory counter on each node - PASS
- 17.10 Counters we added have the correct values - PASS
- 17.11 Add -8 to then get a in-memory counter on each node - PASS
- 17.12 Add 5 to then get a in-memory counter on each node - PASS
- 17.13 Get then add 5 to a in-memory counter on each node - PASS
- 17.14 Counters we added have the correct values - PASS
- 17.15 3 Check counters are consistant across nodes - PASS
- 17.16 4 Counters we added have the correct values - PASS
- 17.17 5 Distributed Set get - PASS
- 17.18 6 Distributed Set size - PASS
- 17.19 7 Distributed Set add() - PASS
- 17.20 8 Distributed Set addAll() - PASS
- 17.21 9 Distributed Set contains() - PASS
- 17.22 10 Distributed Set containsAll() - PASS
- 17.23 11 Distributed Set remove() - PASS
- 17.24 12 Distributed Set removeAll() - PASS
- 17.25 13 Distributed Set addAll() - PASS
- 17.26 14 Distributed Set clear() - PASS
- 17.27 15 Distributed Set addAll() - PASS
- 17.28 16 Distributed Set retain() - PASS
...
- 6.1 Killing ONOS processes - PASS
- 6.2 Checking if ONOS is up yet - PASS
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
- 8.2 Collecting topology information from ONOS - PASS FAIL
- Topology Check Test NOT successful
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
- 3.2 Check app ids - PASS
- 3.3 Discovering Hosts( Via pingall for now ) - PASS FAIL
- Reactive Pingall failed, one or more ping pairs failed
- 3.4 Uninstall reactive forwarding app - PASS
- 3.5 Check app ids - PASS
- 3.6 Add host intents via cli - PASS FAIL
- Error looking up host ids
- 3.7 Intent Anti-Entropy dispersion - PASS
Case 7: Running ONOS Constant State Tests -
...
FAIL
- 7.1 Check that each switch has a master - PASS
- 7.2 Check if switch roles are consistent across all nodes - PASS
- 7.3 Compare switch roles from before failure - PASS FAIL
- Mastership of some switches changed
- 7.4 Get the intents and compare across all nodes - PASS
- 7.5 Get the OF Table entries and compare to before component failure - PASS FAIL
- Changes were found in the flow tables
- 7.6 Leadership Election is still functional - PASS
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 FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS FAIL
- Intents have not been installed correctly, pings failed.
Case 15: Check that Leadership Election is still functional - PASS
...
Test the methods of the distributed primitives (counters and sets) throught the cli
- 17.1 Increment then and get a default counter on each node - PASS
- 17.2 Get then Increment a default counter on each node - PASS
- 17.3 Counters we added have the correct values - PASS
- 17.4 Add -8 to then get a default counter on each node - PASS
- 17.5 Add 5 to then get a default counter on each node - PASS
- 17.6 Get then add 5 to a default counter on each node - PASS
- 17.7 Counters we added have the correct values - PASS
- 17.8 Increment and get an in - memory counter on each node - PASS
- 17.9 Get then Increment a in-memory counter on each node - PASS
- 17.10 Counters we added have the correct values - PASS
- 17.11 Add -8 to then get a in-memory counter on each node - PASS
- 17.12 Add 5 to then get a in-memory counter on each node - PASS
- 17.13 Get then add 5 to a in-memory counter on each node - PASS
- 17.14 Counters we added have the correct values - PASS
- 17.15 3 Check counters are consistant across nodes - PASS
- 17.16 4 Counters we added have the correct values - PASS
- 17.17 5 Distributed Set get - PASS
- 17.18 6 Distributed Set size - PASS
- 17.19 7 Distributed Set add() - PASS
- 17.20 8 Distributed Set addAll() - PASS
- 17.21 9 Distributed Set contains() - PASS
- 17.22 10 Distributed Set containsAll() - PASS
- 17.23 11 Distributed Set remove() - PASS
- 17.24 12 Distributed Set removeAll() - PASS
- 17.25 13 Distributed Set addAll() - PASS
- 17.26 14 Distributed Set clear() - PASS
- 17.27 15 Distributed Set addAll() - PASS
- 17.28 16 Distributed Set retain() - PASS
...
- 9.1 Kill Link between s3 and s28 - PASS
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
- 8.2 Collecting topology information from ONOS - PASS FAIL
- Topology Check Test NOT successful
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 FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS 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 s3 and s28 back up - PASS
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
- 8.2 Collecting topology information from ONOS - PASS FAIL
- Topology Check Test NOT successful
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 FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS 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 -
...
FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS FAIL
- Topology Check Test NOT successful
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 FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS 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 -
...
FAIL
Compare topology objects between Mininet and ONOS
- 8.1 Comparing ONOS topology to MN - No Result
- 8.2 Collecting topology information from ONOS - PASS FAIL
- Topology Check Test NOT successful
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 FAIL
- Intents have not been installed correctly, pings failed.
- 4.2 Check Intent state - PASS FAIL
- Intents are not all in INSTALLED state
- 4.3 Check leadership of topics - PASS
- 4.4 Wait a minute then ping again - PASS FAIL
- Intents have not been installed correctly, pings failed.
Case 13: Test Cleanup - PASS
...
- 13.1 Killing tcpdumps - No Result
- 13.2 Copying MN pcap and ONOS log files to test station - No Result
- 13.3 Stopping Mininet - PASS
- 13.3 4 Checking ONOS Logs for errors - No Result
- 13.5 Packing and rotating pcap archives - No Result