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/Pipeline_postjob_BM/1860/

...

commit a9017217068ec45ce29b467f9fba349112895375 (HEAD, origin/onos-1.10, onos-1.10)
Author: Andrea Campanella [andrea@opennetworking.org]
AuthorDate: Mon Oct 23 15:46:36 2017 +0200
Commit: Andrea Campanella [andrea@opennetworking.org]
CommitDate: Wed Nov 8 11:45:01 2017 -0800

Fixing Netconf Subscription session reopen

Case 101:

...

Setting up

...

ONOS

...

environment - PASS

Set up ONOS with 3 node(s) ONOS cluster

  • 101.1 Copying config files - PASS (tick)
  • 101.2 Create cell file 101.1 Constructing test variables - No Result (warning)
  • 101.2 Copying config files 3 Applying cell variable to environment - PASS (tick)
  • 101.3 Apply cell to environment 4 Verify cell connectivity - PASS (tick)
  • 101.4 5 Uninstalling ONOS package - PASS (tick)
  • 101.5 6 Creating ONOS package - PASS (tick)
  • 101.6 7 Installing ONOS package - PASS (tick)
  • 101.7 8 Set up ONOS secure SSH - PASS (tick)
  • 101.8 9 Checking if ONOS service is up yet - PASS (tick)
  • 101.9 Starting 10 Checking if ONOS CLI sessions is ready - PASS (tick)
  • 101.10 11 Checking if ONOS CLI is ready for issuing commands - PASS (tick)

...

  • 3.1 Check routes installed - No Result (warning) 3.2 Check routes installed - PASS (tick)
  • 3.3 2 Check M2S intents installed - PASS (tick)
  • 3.4 3 Check whether all flow status are ADDED - PASS (tick)

...

  • 5.1 Bring down the link between sw32 and p64514 - 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 p64515 - 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 p64516 - 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 -

...

PASS

  • 6.1 Bring up the link between sw32 and p64514 - 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 p64515 - 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 p64516 - 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 fail succeed - PASS (tick)
  • 6.12 Check ping between each host pair, expect all to succede=False - FAIL (error)
  • Ping test results are Not expected
  • True - PASS (tick)

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

...

  • 10.1 Check flow entry number in sw1 - FAIL (error)
    • Flow number in sw1 is wrong!
  • 10.2 Check flow entry number in sw7 - FAIL (error)
    • Flow number in sw7 is wrong!
  • 10.3 Start sw11 - PASS (tick)
  • 10.4 Check routes installed - PASS (tick)
  • 10.5 Check M2S intents installed - 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 - PASS (tick)

...