Page History

...

commit 92ed7a17416759f63a05bd1a34e05d5215a68ee4 1a00419e38822df94426d73e1c0904d30a42063d (HEAD, origin/onos-1.6, onos-1.6)
Author: Madan Jampani [madan@onlab.usPrince Pereira [prpereir@partner.ciena.com]
AuthorDate: Tue Jun 21 10:47:56 2016 -0700Fri Jul 8 16:31:58 2016 +0530
Commit: Madan Jampani [madan@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Tue Jun 21 10:48:56 2016 -0700
Fail with StorageException.Unavailable only when client is CLOSEDFri Jul 8 17:37:40 2016 +0000

cherry picking the fix for ONOS-4754 to onos-1.6 and master

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

...

• 1.1 Create cell file - No Result
• 1.2 Applying cell variable to environment - PASS
• 1.3 Verify connectivity to cell - PASS
• 1.4 Setup server for cluster metadata file - PASS
• 1.5 Generate initial metadata file - PASS
• 1.6 Starting Mininet - PASS
• 1.7 Git checkout and pull master - No Result
• 1.8 Using mvn clean install - PASS
• 1.9 Copying backup config files - PASS
• 1.10 Creating ONOS package - PASS
• 1.11 Installing ONOS package - PASS
• 1.12 Checking if ONOS is up yet - PASS
• 1.13 Starting ONOS CLI sessions - PASS
• 1.14 Checking ONOS nodes - PASS
• 1.14 15 Activate apps defined in the params file - No Result
• 1.15 16 Set ONOS configurations - PASS
• 1.16 17 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 -

...

PASS

Compare topology objects between Mininet and ONOS

• 8.1 Comparing ONOS topology to MN topology - FAIL
ONOS topology don't match Mininet
• 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 - FAIL
• ONOS shows 28 SCCs
• PASS
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - FAIL
• Links are incorrect
• PASS
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - FAIL
Nodes check NOT successful
• PASS

Case 21: Assigning Controller roles for switches - PASS

...

• 21.1 Assign mastership of switches to specific controllers - PASS
• 21.2 Check mastership was correctly assigned - PASS

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 ) - 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 - FAIL
• Error looking up host ids
• 3.7 Intent Anti-Entropy dispersion - PASS