Page History

...

commit c5c0d8e441408027a0fbf7075455b474cd505ecb 1fc55d6c57f54a27b6be1755e6502edd4ed44362 (HEAD, origin/onos-1.7, onos-1.7)
Author: Ray Milkey [ray@onlab.usKavitha Alagesan [kalagesa@partner.ciena.com]
AuthorDate: Tue Oct 18 Thu Nov 17 11:1259:50 11 2016 -0700+0530
Commit: Gerrit Code Review [gerrit@onlabSimon Hunt [simon@onlab.us]
CommitDate: Tue Oct 18 23:35:44 Dec 6 17:40:31 2016 +0000

Fix NPE when a POST operation is done for multiple flows and there is no flows array specifiedfor ONOS-5403
--
(cherry picked from commit 131c068323c6e8086f8a009319831ca65704032a21314f093bbf3a6cc380b206419a925d4e7d65c9)

Case 101: Setting up ONOS environment - PASS

...

• 11.1 Check routes installed - PASS
• 11.2 Check M2S intents installed - PASS
• 11.3 Check P2P intents installed - PASS
• 11.4 Check whether all flow status are ADDED - PASS
• 11.5 BGP speakers ping peers, expect all tests to succeed - PASS
• 11.6 BGP speakers ping peers, expect all tests to succeed - PASS
• 11.7 Check ping between each host pair, expect all to succede=True - PASS
• 11.8 Kill speaker1 - PASS
• 11.9 Check routes installed - PASS
• 11.10 Check M2S intents installed - PASS
• 11.11 Check P2P intents installed - PASS
• 11.12 Check whether all flow status are ADDED - PASS
• 11.13 BGP speakers ping peers, expect all tests to succeed - PASS
• 11.14 Check ping between each host pair, expect all to succede=True - PASS

Case 12: Bring down leader ONOS node, check: route number, P2P intent number, M2S intent number, ping test - PASS

• 12.1 Find out ONOS leader node - No Result
• 12.2 Uninstall ONOS/SDN-IP leader node - PASS
• 12.3 Check routes installed - PASS
• 12.4 Check M2S intents installed - PASS
• 12.5 Check P2P intents installed - PASS
• 12.6 Check whether all flow status are ADDED - PASS
• 12.7 BGP speakers ping peers, expect all tests to succeed - PASS
• 12.8 BGP speakers ping peers, expect all tests to succeed - PASS
• 12.9 Check ping between each host pair, expect all to succede=True - PASS