Versions Compared

Old Version 157

changes.mady.by.user Jenkins Technical User

Saved on

compared with

New Version 158

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/ProdHAsingleInstanceRestart/5/

...

commit 619453ba65474796fbdbf23be3c33bb54bb07794 879ed7c6ae0189ff24090cce4609a39d7b43da33 (HEAD, origin/master, origin/HEAD, master)
Author: Madan Jampani [madan@onlab.us]
AuthorDate: Wed Thu Jul 22 23 20:4733:09 08 2015 -0700
Commit: Madan Jampani [madan@onlab.us]
CommitDate: Wed Thu Jul 22 23 20:4733:09 08 2015 -0700
Added missing copyright and license text
Disable the new change notification support as it seems to have caused a regression
HTML
<iframe src="https://onos-jenkins.onlab.us/job/HASingleInstanceRestartHAsingleInstanceRestart/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

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.2 3 Starting Mininet - PASS (tick)
  • 1.3 4 Git checkout and pull master - No Result (warning)
  • 1.4 5 Using mvn clean install - PASS (tick)
  • 1.5 6 Creating ONOS package - PASS (tick)
  • 1.6 7 Installing ONOS package - PASS (tick)
  • 1.7 8 Checking if ONOS is up yet - PASS (tick)
  • 1.8 9 App Ids check - PASS (tick)

Case 2: Assigning devices to controllers - PASS

...

  • 2.1 Assign switches to controllers - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - FAIL (error)
    • Topology Check Test NOT successful
  • PASS (tick)

Case 3: Adding host Intents -

...

PASS

Discover hosts by using pingall then assign predetermined host-to-host intents. After installation, check that the intent is distributed to all nodes and the state is INSTALLED

  • 3.1 Install reactive forwarding app - PASS (tick)
  • 3.2 Check app ids - PASS (tick)
  • 3.3 Discovering Hosts( Via pingall for now ) - FAIL (error)
    • Reactive Pingall failed, one or more ping pairs failed
  • PASS (tick)
  • 3.4 Uninstall reactive forwarding app - PASS (tick)
  • 3.5 Check app ids - PASS (tick)
  • 3.6 Add host intents via cli - FAIL (error)
    • Error looking up host ids
  • PASS (tick)
  • 3.7 Intent Anti-Entropy dispersion - PASS (tick)

Case 4: Verify connectivity by sendind traffic across Intents -

...

PASS

Ping across added host intents to check functionality and check the state of the intent

  • 4.1 Ping across added host intents - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • PASS (tick)
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • PASS (tick)

Case 5: Setting up and gathering data for current state -

...

PASS

  • 5.1 Check that each switch has a master - PASS (tick)
  • 5.2 Get the Mastership of each switch - No Result (warning)
  • 5.3 Get the intents from each controller - No Result (warning)
  • 5.4 Get the flows from each controller - No Result (warning)
  • 5.5 Get the OF Table entries - No Result (warning)
  • 5.6 Collecting topology information from ONOS - No Result (warning)
  • 5.7 Each host has an IP address - PASS (tick)
  • 5.8 There is only one dataplane cluster - PASS (tick)
  • 5.9 Comparing ONOS topology to MN - PASS (tick)
  • 5.10 Device information is correct - FAIL (error)
    • Device information is incorrect
  • PASS (tick)
  • 5.11 Links are correct - FAIL (error)
    • Links are incorrect
  • PASS (tick)
  • 5.12 Hosts are correct - PASS (tick)

...

Test the methods of the distributed primitives (counters and sets) throught the cli

  • 17.1 Increment and then get a default counter on each node - PASS (tick)
  • 17.2 Get then Increment a default counter on each node - PASS (tick)
  • 17.3 Counters we added have the correct values - PASS (tick)
  • 17.4 Add -8 to then get a default counter on each node - PASS (tick)
  • 17.5 Add 5 to then get a default counter on each node - PASS (tick)
  • 17.6 Get then add 5 to a default counter on each node - PASS (tick)
  • 17.7 Counters we added have the correct values - PASS (tick)
  • 17.8 Increment and get an in-memory counter on each node - PASS (tick)
  • 17.9 Get then Increment a in-memory counter on each node - PASS (tick)
  • 17.10 Counters we added have the correct values - PASS (tick)
  • 17.11 Add -8 to then get a in-memory counter on each node - PASS (tick)
  • 17.12 Add 5 to then get a in-memory counter on each node - PASS (tick)
  • 17.13 Get then add 5 to a in-memory counter on each node - PASS (tick)
  • 17.14 Counters we added have the correct values - PASS (tick)
  • 17.15 3 Check counters are consistant across nodes - PASS (tick)
  • 17.4 16 Counters we added have the correct values - PASS (tick)
  • 17.5 17 Distributed Set get - PASS (tick)
  • 17.6 18 Distributed Set size - PASS (tick)
  • 17.7 19 Distributed Set add() - PASS (tick)
  • 17.8 20 Distributed Set addAll() - PASS (tick)
  • 17.9 21 Distributed Set contains() - PASS (tick)
  • 17.10 22 Distributed Set containsAll() - PASS (tick)
  • 17.11 23 Distributed Set remove() - PASS (tick)
  • 17.12 24 Distributed Set removeAll() - PASS (tick)
  • 17.13 25 Distributed Set addAll() - PASS (tick)
  • 17.14 26 Distributed Set clear() - PASS (tick)
  • 17.15 27 Distributed Set addAll() - PASS (tick)
  • 17.16 28 Distributed Set retain() - PASS (tick)

...

  • 6.1 Killing ONOS processes - PASS (tick)
  • 6.2 Checking if ONOS is up yet - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - FAIL (error)
    • Topology Check Test NOT successful
  • PASS (tick)

Case 3: Adding host Intents -

...

PASS

Discover hosts by using pingall then assign predetermined host-to-host intents. After installation, check that the intent is distributed to all nodes and the state is INSTALLED

  • 3.1 Install reactive forwarding app - PASS (tick)
  • 3.2 Check app ids - PASS (tick)
  • 3.3 Discovering Hosts( Via pingall for now ) - FAIL (error)
    • Reactive Pingall failed, one or more ping pairs failed
  • PASS (tick)
  • 3.4 Uninstall reactive forwarding app - PASS (tick)
  • 3.5 Check app ids - PASS (tick)
  • 3.6 Add host intents via cli - FAIL (error)
    • Error looking up host ids
  • PASS (tick)
  • 3.7 Intent Anti-Entropy dispersion - PASS (tick)

Case 7: Running ONOS Constant State Tests -

...

PASS

  • 7.1 Check that each switch has a master - PASS (tick)
  • 7.2 Check if switch roles are consistent across all nodes - PASS (tick)
  • 7.3 Compare switch roles from before failure - FAIL (error)
    • Mastership of some switches changed
  • PASS (tick)
  • 7.4 Get the intents and compare across all nodes - PASS (tick)
  • 7.5 Get the OF Table entries and compare to before component failure - FAIL (error)
    • Changes were found in the flow tables
  • PASS (tick)
  • 7.6 Leadership Election is still functional - PASS (tick)

Case 4: Verify connectivity by sendind traffic across Intents -

...

PASS

Ping across added host intents to check functionality and check the state of the intent

  • 4.1 Ping across added host intents - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • PASS (tick)
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • PASS (tick)

Case 15: Check that Leadership Election is still functional - PASS

...

Test the methods of the distributed primitives (counters and sets) throught the cli

  • 17.1 Increment and then get a default counter on each node - PASS (tick)
  • 17.2 Get then Increment a default counter on each node - PASS (tick)
  • 17.3 Counters we added have the correct values - PASS (tick)
  • 17.4 Add -8 to then get a default counter on each node - PASS (tick)
  • 17.5 Add 5 to then get a default counter on each node - PASS (tick)
  • 17.6 Get then add 5 to a default counter on each node - PASS (tick)
  • 17.7 Counters we added have the correct values - PASS (tick)
  • 17.8 Increment and get an in-memory counter on each node - PASS (tick)
  • 17.9 Get then Increment a in-memory counter on each node - PASS (tick)
  • 17.10 Counters we added have the correct values - PASS (tick)
  • 17.11 Add -8 to then get a in-memory counter on each node - PASS (tick)
  • 17.12 Add 5 to then get a in-memory counter on each node - PASS (tick)
  • 17.13 Get then add 5 to a in-memory counter on each node - PASS (tick)
  • 17.14 Counters we added have the correct values - PASS (tick)
  • 17.15 3 Check counters are consistant across nodes - PASS (tick)
  • 17.4 16 Counters we added have the correct values - PASS (tick)
  • 17.5 17 Distributed Set get - PASS (tick)
  • 17.6 18 Distributed Set size - PASS (tick)
  • 17.7 19 Distributed Set add() - PASS (tick)
  • 17.8 20 Distributed Set addAll() - PASS (tick)
  • 17.9 21 Distributed Set contains() - PASS (tick)
  • 17.10 22 Distributed Set containsAll() - PASS (tick)
  • 17.11 23 Distributed Set remove() - PASS (tick)
  • 17.12 24 Distributed Set removeAll() - PASS (tick)
  • 17.13 25 Distributed Set addAll() - PASS (tick)
  • 17.14 26 Distributed Set clear() - PASS (tick)
  • 17.15 27 Distributed Set addAll() - PASS (tick)
  • 17.16 28 Distributed Set retain() - PASS (tick)

...

  • 9.1 Kill Link between s3 and s28 - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - FAIL (error)
    • Topology Check Test NOT successful
  • PASS (tick)

Case 4: Verify connectivity by sendind traffic across Intents -

...

PASS

Ping across added host intents to check functionality and check the state of the intent

  • 4.1 Ping across added host intents - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • PASS (tick)
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • PASS (tick)

Case 10: Restore a link to ensure that Link Discovery is working properly - PASS

...

  • 10.1 Bring link between s3 and s28 back up - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - FAIL (error)
    • Topology Check Test NOT successful
  • PASS (tick)

Case 4: Verify connectivity by sendind traffic across Intents -

...

PASS

Ping across added host intents to check functionality and check the state of the intent

  • 4.1 Ping across added host intents - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • PASS (tick)
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • PASS (tick)

Case 11: Killing a switch to ensure it is discovered correctly - PASS

  • 11.1 Kill s5 - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - FAIL (error)
    • Topology Check Test NOT successful
  • PASS (tick)

Case 4: Verify connectivity by sendind traffic across Intents -

...

PASS

Ping across added host intents to check functionality and check the state of the intent

  • 4.1 Ping across added host intents - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • PASS (tick)
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • PASS (tick)

Case 12: Adding a switch to ensure it is discovered correctly - PASS

  • 12.1 Add back s5 - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology -

...

PASS

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN - No Result (warning)
  • 8.2 Collecting topology information from ONOS - FAIL (error)
    • Topology Check Test NOT successful
  • PASS (tick)

Case 4: Verify connectivity by sendind traffic across Intents -

...

PASS

Ping across added host intents to check functionality and check the state of the intent

  • 4.1 Ping across added host intents - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • PASS (tick)
  • 4.2 Check Intent state - PASS (tick)
  • 4.3 Check leadership of topics - PASS (tick)
  • 4.4 Wait a minute then ping again - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • PASS (tick)

Case 13: Test Cleanup - PASS

...

  • 13.1 Killing tcpdumps - No Result (warning)
  • 13.2 Copying MN pcap and ONOS log files to test station - No Result (warning) 13.3 Stopping Mininet - PASS (tick)
  • 13.4 3 Checking ONOS Logs for errors - No Result (warning) 13.5 Packing and rotating pcap archives - No Result (warning)