Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://onos-jenkins.onlab.us/job/USECASE_SdnipFunctionCluster/543/

...

commit fbabea0a347db6570e5416d4b7084aac38f25115 1fc55d6c57f54a27b6be1755e6502edd4ed44362 (HEAD, origin/onos-1.7, onos-1.7)
Author: Yixiao Chen Kavitha Alagesan [yixiaokalagesa@partner.chen@huaweiciena.com]
AuthorDate: Wed Sep 14 16:23:24 2016 -0400Thu Nov 17 11:59:11 2016 +0530
Commit: Ray Milkey Simon Hunt [ray@onlabsimon@onlab.us]
CommitDate: Tue Oct 11 12:51:10 2016 -0700
[ONOS-4880][ONOS-5021]IETF TE Topology ProviderDec 6 17:40:31 2016 +0000

Fix for ONOS-5403
--
(cherry picked from commit 21314f093bbf3a6cc380b206419a925d4e7d65c9)

Case 101: Setting up ONOS environment - PASS

...

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

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

...

PASS

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

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

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

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

...

PASS

  • 11.1 Check routes installed - PASS (tick)
  • 11.2 Check M2S intents installed - FAIL (error)
  • M2S intent number is wrong!
  • PASS (tick)
  • 11.3 Check P2P intents installed - PASS (tick)
  • 11.4 Check whether all flow status are ADDED - PASS (tick)
  • 11.5 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 11.6 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 11.7 Check ping between each host pair, expect all to succede=True - FAIL (error)
    • Ping test results are Not expected
  • PASS (tick)
  • 11.8 Kill speaker1 - PASS (tick)
  • 11.9 Check routes installed - PASS (tick)
  • 11.10 Check M2S intents installed - PASS (tick)
  • 11.11 Check P2P intents installed - PASS (tick)
  • 11.12 Check whether all flow status are ADDED - PASS (tick)
  • 11.13 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 11.14 Check ping between each host pair, expect all to succede=True - PASS (tick)

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 (warning)
  • 12.2 Uninstall ONOS/SDN-IP leader node - PASS (tick)
  • 12.3 Check routes installed - PASS (tick)
  • 12.4 Check M2S intents installed - PASS (tick)
  • 12.5 Check P2P intents installed - PASS (tick)
  • 12.6 Check whether all flow status are ADDED - PASS (tick)
  • 12.7 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 12.8 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 12.9 Check ping between each host pair, expect all to succede=True - PASS (tick)