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/HAsanity/28/

...

commit 78b300c7c459a74ebcdc553e2bc315237bebe82c d29847f404f327689e91063d913d39241826b617 (HEAD, origin/master, origin/HEAD, master)
Author: Jon Hall [jhall@onlab.usSho SHIMIZU [sshimizu@us.fujitsu.com]
AuthorDate: Tue Thu Aug 4 1513 09:5210:55 59 2015 -0700
Commit: Gerrit Code Review [gerrit@onlabRay Milkey [ray@onlab.us]
CommitDate: Wed Thu Aug 12 2313 21:4201:34 39 2015 +0000
WIP: Transactional map cli for system tests
Refactor to avoid trivial errors in transactions
--
Include Fixing a bug not to commit the transaction on success

Change-Id: Ie1f823ab6d8fc6f54091d443d24ecc61336155da
HTML
<iframe src="https://onos-jenkins.onlab.us/job/HAsanity/plot/Plot-HA/getPlot?index=0&width=500&height=300"noborder="0" width="500" height="300" scrolling="yes" seamless="seamless"></iframe>

...

  • 2.1 Assign switches to controllers - 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)
  • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.4 Hosts information is correct - PASS (tick)
  • 8.5 Host attachment points to the network - PASS (tick)
  • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
  • 8.7 There is only one SCC - PASS (tick)
  • 8.8 Device information is correct - PASS (tick)FAIL (error)
    • Device information is incorrect
  • 8.9 Links are correct - PASS (tick)
  • 8.10 Hosts are correct - PASS (tick)
  • 8.11 Checking ONOS nodes - PASS (tick)

...

  • 21.1 Assign mastership of switches to specific controllers - PASS (tick)
  • 21.2 Check mastership was correctly assigned - PASS (tick)

Case 8: Compare ONOS Topology view to Mininet topology - PASS

Compare topology objects between Mininet and ONOS

...

  • 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
  • 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 - FAIL (error)
  • Intent ECM anti-entropy took too long
  • PASS (tick)

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

...

Case 6: Wait 60 seconds instead of inducing a failure - PASS

    Case 8: Compare ONOS Topology view to Mininet topology - PASS

    Compare topology objects between Mininet and ONOS

    ...

    • 7.1 Check that each switch has a master - PASS (tick)
    • 7.2 Read device roles from ONOS - PASS (tick)
    • 7.3 Check for consistency in roles from each controller - PASS (tick)
    • 7.4 Compare switch roles from before failure - PASS (tick)
    • 7.5 Get the intents and compare across all nodes - PASS (tick)
    • 7.6 Check for consistency in Intents from each controller - PASS (tick)
    • 7.7 Compare current intents with intents before the failure - PASS (tick)
    • 7.8 Get the OF Table entries and compare to before component failure - PASS (tick)
    • 7.9 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

    ...

    • 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 - PASS (tick)
    • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
    • 8.4 Hosts information is correct - PASS (tick)
    • 8.5 Host attachment points to the network - PASS (tick)
    • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
    • 8.7 There is only one SCC - PASS (tick)
    • 8.8 Device information is correct - PASS (tick)
    • 8.9 Links are correct - PASS (tick)
    • 8.10 Hosts are correct - PASS (tick)
    • 8.11 Checking ONOS nodes - 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 - 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)
    • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
    • 8.4 Hosts information is correct - PASS (tick)
    • 8.5 Host attachment points to the network - PASS (tick)
    • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
    • 8.7 There is only one SCC - PASS (tick)
    • 8.8 Device information is correct - PASS (tick)
    • 8.9 Links are correct - FAIL (error)
      • Links are incorrect
    • 8.10 Hosts are correct - PASS (tick)
    • 8.11 Checking ONOS nodes - 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 - PASS (tick)
    • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
    • 8.4 Hosts information is correct - PASS (tick)
    • 8.5 Host attachment points to the network - PASS (tick)
    • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
    • 8.7 There is only one SCC - PASS (tick)
    • 8.8 Device information is correct - PASS (tick)
    • 8.9 Links are correct - FAIL (error)
    • Links are incorrect
    • PASS (tick)
    • 8.10 Hosts are correct - PASS (tick)
    • 8.11 Checking ONOS nodes - 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 - PASS (tick)
    • 8.3 Hosts view is consistent across all ONOS nodes - PASS (tick)
    • 8.4 Hosts information is correct - PASS (tick)
    • 8.5 Host attachment points to the network - PASS (tick)
    • 8.6 Clusters view is consistent across all ONOS nodes - PASS (tick)
    • 8.7 There is only one SCC - PASS (tick)
    • 8.8 Device information is correct - PASS (tick)
    • 8.9 Links are correct - FAIL (error)
      • Links are incorrect
    • PASS (tick)
    • 8.10 Hosts are correct - PASS (tick)
    • 8.11 Checking ONOS nodes - 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

    ...