Versions Compared

Old Version 34

changes.mady.by.user Jenkins Technical User

Saved on

compared with

New Version 35

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

...

commit 6e4f7eb58c13d762a690257e61099f3df09cd29b f257a96b21e46c596c07284d536b053fd6445dc9 (HEAD, origin/master, origin/HEAD, master)
Author: Carmelo Cascone Simon Hunt [carmelo@opennetworkingsimon@opennetworking.org]
AuthorDate: Mon Fri Aug 21 2325 18:0058:43 47 2017 +0200-0700
Commit: Carmelo Cascone Simon Hunt [carmelo@opennetworkingsimon@opennetworking.org]
CommitDate: Mon Aug 21 2328 02:0025:43 25 2017 +02000000

ONOS-6648 Bumped version of p4c with support for cmake build system6332: Flows: bad parsing of EXTENSION:of:0000nnnn identifier

Case 1:

...

Starting up 3 node(s) ONOS cluster - PASS

Set up ONOS with 3 node(s) ONOS cluster

  • 1.1 Constructing test variables - PASS (tick)

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

  • 1.1 Create cell file - No Result (warning)
  • 1.2 Applying Apply cell variable to environment - No Result (warning)PASS (tick)
  • 1.3 Starting Mininet Uninstalling ONOS package - 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 service - PASS (tick)
  • 1.8 Starting ONOS CLI sessions - PASS (tick)
  • 1.9 Starting Mininet - PASS (tick)
  • 1.10 Activate apps defined in the params file - No Result (warning)
  • 1.10 11 Set ONOS configurations - No Result (warning)
  • 1.11 12 App Ids check - PASS (tick)

Case 2: -

...

PASS

  • 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 - PASS (tick)
  • 2.8 Loading vpls configuration in case any configuration was missed. - PASS (tick)

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

  • 50.1 Check intent states - PASS (tick)
  • 50.2 Testing connectivity... - PASS (tick)

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... - PASS (tick)
  • 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 - PASS (tick)
  • 100.7 Testing connectivity... - PASS (tick)
  • 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... - PASS (tick)
  • 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... - PASS (tick)
  • 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 - PASS (tick)
  • 100.21 Testing connectivity... - PASS (tick)
  • 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 - PASS (tick)
  • 100.28 Testing connectivity... - PASS (tick)
  • 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... - PASS (tick)
  • 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 - PASS (tick)
  • 100.35 Testing connectivity... - PASS (tick)
  • 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... - PASS (tick)
  • 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... - PASS (tick)

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... - PASS (tick)
  • 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.

Case 300: Stop one ONOS node at a time and test connectivity. - FAIL

  • 300.1 Stop ONOS node 0. - PASS (tick)
  • 300.2 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 300.3 Restart ONOS node 0 and checking status of restart. - PASS (tick)
  • 300.4 Checking ONOS nodes. - FAIL (error)
    • Apps are NOT the same across all nodes.
  • 300.5 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 300.6 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 300.7 Stop ONOS node 1. - PASS (tick)
  • 300.8 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 300.9 Restart ONOS node 1 and checking status of restart. - PASS (tick)
  • 300.10 Checking ONOS nodes. - FAIL (error)
    • Apps are NOT the same across all nodes.
  • 300.11 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 300.12 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 300.13 Stop ONOS node 2. - PASS (tick)
  • 300.14 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 300.15 Restart ONOS node 2 and checking status of restart. - PASS (tick)
  • 300.16 Checking ONOS nodes. - FAIL (error)
    • Apps are NOT the same across all nodes.
  • 300.17 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 300.18 Testing connectivity... - FAIL (error)
    • Connectivity is NOT as expected.

Case 310: Kill one ONOS node at a time and test connectivity. - FAIL

  • 310.1 Killing ONOS node 1. - PASS (tick)
  • 310.2 Waiting for ONOS to restart. - No Result (warning)
  • 310.3 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 310.4 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 310.5 Killing ONOS node 2. - PASS (tick)
  • 310.6 Waiting for ONOS to restart. - No Result (warning)
  • 310.7 Check intent states - FAIL (error)
    • Not all Intents in installed state
  • 310.8 Testing connectivity... - FAIL (error)
    • Connectivity failed.
  • 310.9 Killing ONOS node 3. - PASS (tick)
  • 310.10 Waiting for ONOS to restart. - No Result (warning)
  • 310.11 Check intent states - PASS (tick)
  • 310.12 Testing connectivity... - FAIL (error)
    • Connectivity is NOT as expected.

Case 400: Bring down one link at a time and test connectivity. - FAIL