Page History

...

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

commit 581c8407e613a27aaa573a600828b30a37066fb8

...

commit eb5eebbb820c0a623f0fbbae1ac3b3149ad13324 (HEAD, origin/master, origin/HEAD, master)
Author: Sanjay S pierventre [sanjaypier@opennetworking.s@happiestminds.comorg]
AuthorDate: Fri Apr 24 15:44:50 2015 +0530
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Thu Apr 30 04:04:11 2015 +0000
Modified to accommodate code review comments.

<iframe src="https://onos-jenkins.onlab.us/job/HASingleInstanceRestart/plot/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

Case 1: Setting up test environment - PASSED

Thu Sep 23 19:03:14 2021 +0200
Commit: Pier Luigi Ventre [pier@opennetworking.org]
CommitDate: Mon Sep 27 19:27:55 2021 +0000

[SDFAB-616] Inconsistent format of port number in DhcpRelay
--
(cherry picked from commit 61bd673eec2282aff175daff141059870db78c7d)

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

For loading from params file, and pull and build the latest ONOS package

• 1.1 Constructing test variables - PASS
• 1.2 Apply cell to environment - PASS
• 1.3 Uninstalling Atomix - PASS
• 1.4 Uninstalling ONOS package - PASS
• 1.5 Apply cell to environment - PASS
• 1.6 Starting Mininet - PASS
• 1.7 Creating ONOS package - PASS
• 1.8 Installing Atomix - PASS
• 1.9 Installing ONOS package - PASS
• 1.10 Set up ONOS secure SSH - PASS
• 1.11 Checking ONOS service - PASS
• 1.12 Starting ONOS CLI sessions - PASS
• 1.13 Checking ONOS nodes - PASS
• 1.14 Checking ONOS applications - PASS
• 1.15 Checking ONOS nodes - PASS
• 1.16 Activate apps defined in the params file - No Result
• 1.17 Set ONOS configurations - PASS
• 1.18 Check app ids - PASS
• 1.19 Set logging levels
• 1.1 Applying cell variable to environment - No Result
• 1.2 Starting Mininet - No Result
• 1.3 Compiling the latest version of ONOS - No Result
• 1.4 Creating ONOS package - No Result
• 1.5 Installing ONOS package - No Result
• 1.6 Checking if ONOS is up yet - No Result
• 1.7 Start Packet Capture MN - PASS

Case 2: Assigning

...

devices to controllers - PASS

Assign switches to ONOS using 'ovs-vsctl' and check that an ONOS node becomes the master of the device.

• 2.1 Assign switches to controllers - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - No Result 8.2 Comparing ONOS topology to MN topology - No Result PASS
• 8.3 Collecting topology information from ONOS 2 Checking ONOS nodes - PASS

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
• 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 2 Add host intents via cli - PASS
• 3.7 Intent Anti-Entropy dispersion - PASS

Case 4: Verify connectivity by sending traffic across Intents - PASS

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 5: Setting up and gathering data for current state -

...

PASS

• 5.1 Check that each switch has a master - PASS
• 5.2 Get the intents 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
• 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 - No Result PASS
• 5.8 Check for consistency in Flows from each controller - PASS
• 5.4 9 Get the OF Table entries - No Result
• 5.5 Create TestONTopology object 10 Start continuous pings - No Result
• 5.6 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.7 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

Case 14: Start Leadership Election app - PASS

• 14.1 Install leadership election app - PASS
• 14.2 Run for election on each node - PASS
• 14.3 Active node was elected leader? - 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 16: Install Primitives app -

...

PASS

• 16.1 Install Primitives app - PASS

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 and then get a default counter on each node - PASS
• 17.2 Increment and get an in memory Get then Increment a default counter on each node - PASS
• 17.3 Check counters are consistant across nodes 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.5 8 Distributed Set get - PASS
• 17.6 9 Distributed Set size - PASS
• 17.7 10 Distributed Set add() - PASS
• 17.8 11 Distributed Set addAll() - PASS
• 17.9 12 Distributed Set contains() - PASS
• 17.10 13 Distributed Set containsAll() - PASS
• 17.11 14 Distributed Set remove() - PASS
• 17.12 15 Distributed Set removeAll() - PASS
• 17.13 16 Distributed Set addAll() - PASS
• 17.14 17 Distributed Set clear() - PASS
• 17.15 18 Distributed Set addAll() - PASS
• 17.16 19 Distributed Set retain() - FAIL
• Set retain was incorrect
• 17.20 Partitioned Transactional maps put - PASS
• 17.21 Partitioned Transactional maps get - PASS
• 17.22 Get the value of a new value - PASS
• 17.23 Atomic Value set() - PASS
• 17.24 Get the value after set() - PASS
• 17.25 Atomic Value compareAndSet() - PASS
• 17.26 Get the value after compareAndSet() - PASS
• 17.27 Atomic Value getAndSet() - PASS
• 17.28 Get the value after getAndSet() - PASS
• 17.29 Atomic Value destory() - PASS
• 17.30 Get the value after destroy() - PASS
• 17.31 Work Queue add() - PASS
• 17.32 Check the work queue stats - PASS
• 17.33 Work Queue addMultiple() - PASS
• 17.34 Check the work queue stats - PASS
• 17.35 Work Queue takeAndComplete() 1 - PASS
• 17.36 Check the work queue stats - PASS
• 17.37 Work Queue takeAndComplete() 2 - PASS
• 17.38 Check the work queue stats - PASS
• 17.39 Work Queue destroy() - PASS
• 17.40 Check the work queue stats - PASS

Case 6:

...

Restart ONOS node - PASS

Killing ONOS process and restart cli sessions once onos is up.

• 6.1 Checking ONOS Logs for errors - No Result
• 6.2 Killing ONOS processes - PASS
• 6.3 Checking if ONOS is up yet - PASS
• 6.4 Starting ONOS CLI sessions - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - No Result 8.2 Comparing ONOS topology to MN topology - No Result PASS
• 8.3 Collecting topology information from ONOS 2 Checking ONOS nodes - PASS

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
• 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 2 Add host intents via cli - PASS
• 3.7 Intent Anti-Entropy dispersion - PASS

Case 7: Running ONOS Constant State Tests -

...

PASS

• 7.1 Check if switch roles are consistent across all nodes 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.2 4 Compare switch roles from before failure - PASS
• 7.3 5 Get the intents and compare across all nodes from each controller - PASS
• 7.4 Get the OF Table entries and compare to before component failure - FAIL

...

• 6 Check for consistency in Intents from each controller - PASS

Case 4: Verify connectivity by sending traffic across Intents - PASS

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 - FAIL PASS
• 15.4 Check that a new node was elected leader - PASS
• 15.2 Make sure new leader is elected - FAIL 5 Check that that new leader was the candidate of old leader - PASS
• 15.3 6 Run for election on old leader( just so everyone is in the hat ) - FAIL 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

• 17.1 Increment and then get a default counter on each node - PASS
• 17.2 Increment and get an in memory Get then Increment a default counter on each node - PASS
• 17.3 Check counters are consistant across nodes 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.5 8 Distributed Set get - PASS FAIL
• Set elements are incorrect
• 17.6 9 Distributed Set size - PASS FAIL
• Set sizes are incorrect
• 17.7 10 Distributed Set add() - PASS
• 17.8 11 Distributed Set addAll() - PASS
• 17.9 12 Distributed Set contains() - PASS
• 17.10 13 Distributed Set containsAll() - PASS
• 17.11 14 Distributed Set remove() - PASS
• 17.12 15 Distributed Set removeAll() - PASS
• 17.13 16 Distributed Set addAll() - PASS
• 17.14 17 Distributed Set clear() - PASS
• 17.15 18 Distributed Set addAll() - PASS
• 17.16 Distributed Set retain() - PASS 19 Distributed Set retain() - FAIL
• Set retain was incorrect
• 17.20 Partitioned Transactional maps put - PASS
• 17.21 Partitioned Transactional maps get - PASS
• 17.22 Get the value of a new value - PASS
• 17.23 Atomic Value set() - PASS
• 17.24 Get the value after set() - PASS
• 17.25 Atomic Value compareAndSet() - PASS
• 17.26 Get the value after compareAndSet() - PASS
• 17.27 Atomic Value getAndSet() - PASS
• 17.28 Get the value after getAndSet() - PASS
• 17.29 Atomic Value destory() - PASS
• 17.30 Get the value after destroy() - PASS
• 17.31 Work Queue add() - PASS
• 17.32 Check the work queue stats - PASS
• 17.33 Work Queue addMultiple() - PASS
• 17.34 Check the work queue stats - PASS
• 17.35 Work Queue takeAndComplete() 1 - PASS
• 17.36 Check the work queue stats - PASS
• 17.37 Work Queue takeAndComplete() 2 - PASS
• 17.38 Check the work queue stats - PASS
• 17.39 Work Queue destroy() - PASS
• 17.40 Check the work queue stats - PASS

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

...

PASS

• 9.1 Kill Link between s28 and s3 and s28 - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - No Result 8.2 Comparing ONOS topology to MN topology - No Result PASS
• 8.3 Collecting topology information from ONOS 2 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sending traffic across Intents - PASS

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 10: Restore a link to ensure that Link Discovery is working properly -

...

PASS

• 10.1 Bring link between s28 and s3 and s28 back up - PASS

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Create TestONTopology object - No Result 8.2 Comparing ONOS topology to MN topology - No Result PASS
• 8.3 Collecting topology information from ONOS 2 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sending traffic across Intents - PASS

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 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 Create TestONTopology object - No Result 8.2 Comparing ONOS topology to MN topology - No Result PASS
• 8.3 Collecting topology information from ONOS 2 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sending traffic across Intents - PASS

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 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 Create TestONTopology object - No Result 8.2 Comparing ONOS topology to MN topology - No Result PASS
• 8.3 Collecting topology information from ONOS 2 Checking ONOS nodes - PASS

Case 4: Verify connectivity by sending traffic across Intents - PASS

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 13: Test Cleanup -

...

PASS

• 13.1 Killing tcpdumps - No Result Checking raft log size - PASS
• 13.2 Copying MN pcap and ONOS log files to test station Killing tcpdumps - No Result
• 13.3 Stopping Mininet - No Result 13.4 Checking ONOS Logs for errors - No Result
• 13.5 Packing and rotating pcap archives 4 Stopping Mininet - PASS