Have questions? Stuck? Please check our FAQ for some common questions and answers.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

VPLSfailsafe at 05 Aug 2017 22:54:06

commit a028a2c61c696d33c81e4fc4e12a9e8d9e6c5091 (HEAD, origin/master, origin/HEAD, master)
Author: Yuta HIGUCHI [y-higuchi@ak.jp.nec.com]
AuthorDate: Sat Aug 5 15:43:15 2017 -0700
Commit: Yuta HIGUCHI [y-higuchi@ak.jp.nec.com]
CommitDate: Sat Aug 5 15:43:15 2017 -0700

incubator-core no longer exists

Case 1: Setting up test environment - PASS

Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.

  • 1.1 Create cell file - No Result (warning)
  • 1.2 Applying cell variable to environment - No Result (warning)
  • 1.3 Starting Mininet - PASS (tick)
  • 1.4 Creating ONOS package - PASS (tick)
  • 1.5 Installing ONOS package - PASS (tick)
  • 1.6 Set up ONOS secure SSH - PASS (tick)
  • 1.7 Checking if ONOS is up yet - PASS (tick)
  • 1.8 Starting ONOS CLI sessions - PASS (tick)
  • 1.9 Activate apps defined in the params file - No Result (warning)
  • 1.10 Set ONOS configurations - No Result (warning)
  • 1.11 App Ids check - PASS (tick)

Case 2: - FAIL

  • 2.1 Discover hosts using pings - No Result (warning)
  • 2.2 Load VPLS configurations - PASS (tick)
  • 2.3 Check VPLS configurations - PASS (tick)
  • 2.4 Check interface configurations - PASS (tick)
  • 2.5 Check network configurations for vpls application - PASS (tick)
  • 2.6 Check vpls app configurations - PASS (tick)
  • 2.7 Check connectivity - FAIL (error)
    • Connectivity is not as expected
  • 2.8 Loading vpls configuration in case any configuration was missed. - PASS (tick)

Case 50: Check connectivity before running all other tests. - FAIL

  • 50.1 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 50.2 Testing connectivity... - FAIL (error)
    • Connectivity is NOT as expected.

Case 100: Bring down one host at a time and test connectivity. - FAIL

  • 100.1 Kill link between s1 and h1. - PASS (tick)
  • 100.2 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.3 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 100.4 Re-adding link between s1 and h1. - PASS (tick)
  • 100.5 Discover h1 using ping. - No Result (warning)
  • 100.6 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.7 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 100.8 Kill link between s2 and h2. - PASS (tick)
  • 100.9 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.10 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 100.11 Re-adding link between s2 and h2. - PASS (tick)
  • 100.12 Discover h2 using ping. - No Result (warning)
  • 100.13 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.14 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 100.15 Kill link between s3 and h3. - PASS (tick)
  • 100.16 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.17 Testing connectivity... - PASS (tick)
  • 100.18 Re-adding link between s3 and h3. - PASS (tick)
  • 100.19 Discover h3 using ping. - No Result (warning)
  • 100.20 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.21 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 100.22 Kill link between s4 and h4. - PASS (tick)
  • 100.23 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.24 Testing connectivity... - PASS (tick)
  • 100.25 Re-adding link between s4 and h4. - PASS (tick)
  • 100.26 Discover h4 using ping. - No Result (warning)
  • 100.27 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.28 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 100.29 Kill link between s5 and h5. - PASS (tick)
  • 100.30 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.31 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 100.32 Re-adding link between s5 and h5. - PASS (tick)
  • 100.33 Discover h5 using ping. - No Result (warning)
  • 100.34 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.35 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 100.36 Kill link between s6 and h6. - PASS (tick)
  • 100.37 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.38 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 100.39 Re-adding link between s6 and h6. - PASS (tick)
  • 100.40 Discover h6 using ping. - No Result (warning)
  • 100.41 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.42 Testing connectivity... - FAIL (error)
    • Connectivity is NOT as expected.

Case 200: Bring down one switch at a time and test connectivity. - FAIL

  • 200.1 Delete s5. - PASS (tick)
  • 200.2 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 200.3 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 200.4 Add s5. - PASS (tick)
  • 200.5 Reconnecting links on s5. - No Result (warning)
  • 200.6 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 200.7 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 200.8 Delete s6. - FAIL (error)
    • Failed to delete switch.
  • 200.9 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 200.10 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 200.11 Add s6. - FAIL (error)
    • Failed to add switch.
  • 200.12 Reconnecting links on s6. - No Result (warning)
  • 200.13 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 200.14 Testing connectivity... - FAIL (error)
    • Connectivity is NOT as expected.
  • No labels