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/HAsingleInstanceRestart/59/

...

commit 726dc5baab7a5634efaf87beb343a751cf7dfd9d d6c965dc65a04f99d68afe57172c9150091e0eaf (HEAD, origin/master, origin/HEAD, master)
Author: Brian O'Connor [bocon@onlabThomas Vachuska [tom@onlab.us]
AuthorDate: Sat Tue Sep 5 008 20:1348:07 58 2015 -0700
Commit: Brian O'Connor [bocon@onlabThomas Vachuska [tom@onlab.us]
CommitDate: Sat Tue Sep 5 008 20:1348:07 58 2015 -0700
Adding set -e to onos-archetypes-test
Added shutdown hook to STC to print summary even when interrupted by user.
HTML
<iframe src="https://onos-jenkins.onlab.us/job/HAsingleInstanceRestart/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

  • 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 -

...

FAIL

Compare topology objects between Mininet and ONOS

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

Case 3: Adding host Intents -

...

FAIL

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 ) - PASS (tick)FAIL (error)
    • Reactive Pingall failed, one or more ping pairs failed
  • 3.4 Uninstall reactive forwarding app - PASS (tick)
  • 3.5 Check app ids - PASS (tick)
  • 3.6 Add host intents via cli - PASS (tick)
  • 3.7 Intent Anti-Entropy dispersion - PASS (tick)

...

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

Case 8: Compare ONOS Topology view to Mininet topology -

...

FAIL

Compare topology objects between Mininet and ONOS

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

Case 4: Verify connectivity by sendind traffic across Intents - PASS

...

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

Case 8: Compare ONOS Topology view to Mininet topology -

...

FAIL

Compare topology objects between Mininet and ONOS

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

Case 4: Verify connectivity by sendind traffic across Intents - PASS

...

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 -

...

FAIL

Compare topology objects between Mininet and ONOS

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

Case 4: Verify connectivity by sendind traffic across Intents - PASS

...

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 -

...

FAIL

Compare topology objects between Mininet and ONOS

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

Case 4: Verify connectivity by sendind traffic across Intents - PASS

...