Page History

...

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

commit 05acc713ac764f932179172528665c5ee6efe99c 8eb1025c98cf3ee33928e4d1fea771ae4399bdf9 (HEAD -] onos-1.11, origin/onos-1.11)
Author: ONOS Jenkins User [jenkins@onlab.usRay Milkey [ray@opennetworking.org]
AuthorDate: Tue Mar 27 1713:3858:17 08 2018 +0000-0700
Commit: ONOS Jenkins User [jenkins@onlab.usRay Milkey [ray@opennetworking.org]
CommitDate: Tue Mar 27 17:38:17 Thu Apr 5 23:37:07 2018 +0000
Starting snapshot 1.11.3-SNAPSHOT
Fix bug when publishing maintenance release docs
--
(cherry picked from commit 859e04187624c3f01919b37584a98d7e92993884)

Case 1:

...

Constructing test variables and building ONOS package - FAIL

For loading from params file, and pull and build the latest ONOS packageSet up ONOS with 1 node(s) ONOS cluster

• 1.1 Constructing test variables - PASS
• 1.2 Apply cell to environment - PASS
• 1.3 Uninstalling ONOS package - PASS
• 1.4 Apply cell to environment - PASS
• 1.5 Starting Mininet - PASS
• 1.6 Apply cell to environment - PASS 1.7 Creating Creating ONOS package - PASS
• 1.8 7 Installing ONOS package - PASS
• 1.9 8 Set up ONOS secure SSH - PASS
• 1.10 9 Checking ONOS service - PASS
• 1.11 10 Starting ONOS CLI sessions - PASS
• 1.12 11 Checking ONOS nodes - PASS
• 1.13 12 Activate apps defined in the params file - No Result
• 1.14 13 Set ONOS configurations - FAIL
• Failed to set config
• 1.14 Check app ids - PASS
• 1.15 Check app ids Set logging levels - PASS

Case 2: Assigning devices to controllers - PASS

...

• 5.1 Check that each switch has a master - No Result PASS
• 5.2 Check that each switch has a master - PASS 5.3 Get the Mastership of each switch Get the Mastership of each switch from each controller - No Result
• 5.4 3 Read device roles from ONOS - PASS
• 5.5 4 Check for consistency in roles from each controller - PASS
• 5.6 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.9 Get the OF Table entries - No Result
• 5.10 Start continuous pings - No Result
• 5.9 11 Collecting topology information from ONOS - No Result
• 5.12 Host view is consistent across ONOS nodes - PASS
• 5.10 13 Each host has an IP address - PASS
• 5.11 There is only one dataplane cluster 14 Cluster view is consistent across ONOS nodes - PASS
• 5.15 Cluster view correct across ONOS nodes - PASS
• 5.12 16 Comparing ONOS topology to MN - PASS
• 5.13 17 Device information is correct - PASS
• 5.14 18 Links are correct - PASS
• 5.15 19 Hosts are correct - PASS
• 5.16 Read device roles from ONOS - PASS
• 5.17 Check for consistency in roles from each controller - PASS

Case 14: Start Leadership Election app - PASS

...

• 7.1 Check that each switch has a master - PASS 7.2 Check if switch roles are consistent across all nodes - No Result
• 7.3 2 Read device roles from ONOS - PASS
• 7.4 3 Check for consistency in roles from each controller - PASS
• 7.5 4 Compare switch roles from before failure - PASS
• 7.6 5 Get the intents and compare across all nodes from each controller - PASS
• 7.7 Get the OF Table entries and compare to before component failure 6 Check for consistency in Intents from each controller - PASS
• 7.8 Leadership Election is still functional - PASS

Case 4: Verify connectivity by sending traffic across Intents - 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

...

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

...