Versions Compared

Old Version 1

changes.mady.by.user Jenkins Technical User

Saved on

compared with

New Version 2

changes.mady.by.user Jenkins Technical User

Saved on

Key

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

...

commit b0734599424c869860725e421f3aac9fa5a26c45 (HEAD, origin/master, origin/HEAD, master)
Author: Thomas Vachuska [tom@opennetworking.org]
AuthorDate: Tue Jul 18 17:13:01 2017 -0700
Commit: Thomas Vachuska [tom@opennetworking.org]
CommitDate: Tue Jul 18 17:13:01 2017 -0700

Adding utility to provide STC warden status.

Case 1: Setting up test environment - FAIL

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 - FAIL (error)
    • Error starting Mininet
  • 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. - FAIL (error)
    • Failed to bring link down.
  • 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. - FAIL (error)
    • Failed to bring link up.
  • 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. - FAIL (error)
    • Failed to bring link down.
  • 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. - FAIL (error)
    • Failed to bring link up.
  • 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. - FAIL (error)
    • Failed to bring link down.
  • 100.16 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.17 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 100.18 Re-adding link between s3 and h3. - FAIL (error)
    • Failed to bring link up.
  • 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. - FAIL (error)
    • Failed to bring link down.
  • 100.23 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 100.24 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 100.25 Re-adding link between s4 and h4. - FAIL (error)
    • Failed to bring link up.
  • 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. - FAIL (error)
    • Failed to bring link down.
  • 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. - FAIL (error)
    • Failed to bring link up.
  • 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. - FAIL (error)
    • Failed to bring link down.
  • 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. - FAIL (error)
    • Failed to bring link up.
  • 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.