Page History

...

commit fbabea0a347db6570e5416d4b7084aac38f25115 c5c0d8e441408027a0fbf7075455b474cd505ecb (HEAD, origin/onos-1.7, onos-1.7)
Author: Yixiao Chen Ray Milkey [yixiaoray@onlab.chen@huawei.comus]
AuthorDate: Wed Sep 14 16:23:24 2016 -0400Tue Oct 18 11:12:50 2016 -0700
Commit: Ray Milkey [ray@onlabGerrit Code Review [gerrit@onlab.us]
CommitDate: Tue Oct 11 1218 23:5135:10 2016 -0700
[ONOS-4880][ONOS-5021]IETF TE Topology Provider44 2016 +0000

Fix NPE when a POST operation is done for multiple flows and there is no flows array specified
--
(cherry picked from commit 131c068323c6e8086f8a009319831ca65704032a)

Case 101: Setting up ONOS environment - PASS

...

• 7.1 Stop sw32 - PASS
• 7.2 Check routes installed - PASS
• 7.3 Check M2S intents installed - PASS
• 7.4 Check P2P intents installed - PASS
• 7.5 Check ping between hosts behind BGP peers - PASS
• 7.6 Check ping between BGP peers and speaker1 - PASS
• 7.7 Check ping between BGP peers and speaker2 - PASS
• 7.8 Check whether all flow status are ADDED - PASS

Case 8: Start the edge sw32, check P-2-P and M-2-S intents, ping test -

...

PASS

• 8.1 Start sw32 - PASS
• 8.2 Check routes installed - PASS
• 8.3 Check M2S intents installed - FAIL
• M2S intent number is wrong!
• PASS
• 8.4 Check P2P intents installed - PASS
• 8.5 Check whether all flow status are ADDED - PASS
• 8.6 BGP speakers ping peers, expect all tests to succeed - PASS
• 8.7 BGP speakers ping peers, expect all tests to succeed - PASS
• 8.8 Check ping between each host pair, expect all to succede=True - FAIL
Ping test results are Not expected
• PASS

Case 9: Stop sw11 located in best path, check route number, P2P intent number, M2S intent number, ping test -

...

PASS

• 9.1 Check flow entry number in sw11 - FAIL
• Flow number in sw11 is wrong!
• PASS
• 9.2 Check flow entry number in sw1 - PASS
• 9.3 Check flow entry number in sw7 - PASS
• 9.4 Stop sw11 - PASS
• 9.5 Check routes installed - PASS
• 9.6 Check M2S intents installed - FAIL
• M2S intent number is wrong!
• PASS
• 9.7 Check P2P intents installed - PASS
• 9.8 Check whether all flow status are ADDED - PASS
• 9.9 BGP speakers ping peers, expect all tests to succeed - PASS
• 9.10 BGP speakers ping peers, expect all tests to succeed - PASS
• 9.11 Check ping between each host pair, expect all to succede=True - FAIL
Ping test results are Not expected
• PASS

Case 10: Start sw11 which was stopped in CASE9, check route number, P2P intent number, M2S intent number, ping test -

...

PASS

• 10.1 Check flow entry number in sw1 - FAIL
Flow number in sw1 is wrong!
• PASS
• 10.2 Check flow entry number in sw7 - PASS
• 10.3 Start sw11 - PASS
• 10.4 Check routes installed - PASS
• 10.5 Check M2S intents installed - FAIL
• M2S intent number is wrong!
• PASS
• 10.6 Check P2P intents installed - PASS
• 10.7 Check whether all flow status are ADDED - PASS
• 10.8 BGP speakers ping peers, expect all tests to succeed - PASS
• 10.9 BGP speakers ping peers, expect all tests to succeed - PASS
• 10.10 Check ping between each host pair, expect all to succede=True - FAIL
• Ping test results are Not expected
• PASS

Case 11: Kill speaker1, check:route number, P2P intent number, M2S intent number, ping test -

...

PASS

• 11.1 Check routes installed - PASS
• 11.2 Check M2S intents installed - FAIL
M2S intent number is wrong!
• 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 - FAIL
Ping test results are Not expected
• 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

...