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/526/

...

commit 00ded542dbf467097f38dd5006c8904a18e06434 ea4cc17a922df637a5598c058bad15265c506c78 (HEAD, origin/onos-1.7, onos-1.7)
Author: Kavitha Alagesan Jayasree Ghosh [kalagesa@partnerjghosh@partner.ciena.com]
AuthorDate: Thu Tue Nov 10 168 19:1155:32 47 2016 +0530
Commit: Gerrit Code Review [gerrit@onlab.us]
CommitDate: Mon Fri Nov 14 0918 16:1613:10 50 2016 +0000
FIX_FOR_ONOS-5610
Fix for ONOS-5566:Issue With Region POST-DELETE REST API:Incorporated Comments

Case 101: Setting up ONOS environment - PASS

...

  • 5.1 Bring down the link between sw32 and peer64514 - PASS (tick)
  • 5.2 Check routes installed - PASS (tick)
  • 5.3 Check M2S intents installed - PASS (tick)
  • 5.4 Bring down the link between sw8 and peer64515 - PASS (tick)
  • 5.5 Check routes installed - PASS (tick)
  • 5.6 Check M2S intents installed - PASS (tick)
  • 5.7 Bring down the link between sw28 and peer64516 - PASS (tick)
  • 5.8 Check routes installed - PASS (tick)
  • 5.9 Check M2S intents installed - PASS (tick)
  • 5.10 Check whether all flow status are ADDED - PASS (tick)
  • 5.11 BGP speakers ping peers, expect all tests to fail - PASS (tick)
  • 5.12 Check ping between each host pair, expect all to succede=False - PASS (tick)

Case 6: Bring up links and check routes/intents -

...

FAIL

  • 6.1 Bring up the link between sw32 and peer64514 - PASS (tick)
  • 6.2 Check routes installed - PASS (tick)
  • 6.3 Check M2S intents installed - PASS (tick)
  • 6.4 Bring up the link between sw8 and peer64515 - PASS (tick)
  • 6.5 Check routes installed - PASS (tick)
  • 6.6 Check M2S intents installed - PASS (tick)
  • 6.7 Bring up the link between sw28 and peer64516 - PASS (tick)
  • 6.8 Check routes installed - PASS (tick)
  • 6.9 Check M2S intents installed - PASS (tick)
  • 6.10 Check whether all flow status are ADDED - PASS (tick)
  • 6.11 BGP speakers ping peers, expect all tests to succeed - PASS (tick)
  • 6.12 Check ping between each host pair, expect all to succede=True - PASS (tick)FAIL (error)
    • Ping test results are Not expected

Case 7: Stop edge sw32,check P-2-P and M-2-S intents, ping test - PASS

...

  • 11.1 Check routes installed - PASS (tick)
  • 11.2 Check M2S intents installed - 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 - 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)