Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published from Jenkins build: https://jenkins.onosproject.org/job/HA-pipeline-master/1391/

...

HTML
<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/HAfullNetPartition_master_20-builds_graph.jpg", alt="HAfullNetPartition", style="width:525px;height:350px;border:0">

commit fbf61433358e2eeeae209e62736032ddf22f0fd2 40259008bd569af9d11d3ea784c757fd47187e78 (HEAD -] master, origin/master, origin/HEAD)
Author: jaegonkim DongRyeol Cha [jaegon77dr83.kim@samsungcha@samsung.com]
AuthorDate: Sat Fri Mar 16 0915 18:3726:53 11 2019 +0900
Commit: jaegonkim Andrea Campanella [jaegon77andrea@opennetworking.kim@samsung.comorg]
CommitDate: Sat Tue Mar 16 0919 04:3827:43 24 2019 +0900
[ONOS-7732] Automating switch workflow: workflow cli command completeter0000

Restart the scheduled task when polling frequency is really changed

Case 1: Constructing test variables and building ONOS package - PASS

...

  • 62.1 Deleteing firewall rules - PASS (tick)
  • 62.2 Checking ONOS nodes - 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 topology - FAIL (error)
  • ONOS topology don't match Mininet
  • PASS (tick)
  • 8.2 Hosts view is consistent across all ONOS nodes - PASS (tick)
  • 8.3 Hosts information is correct - PASS (tick)
  • 8.4 Host attachment points to the network - PASS (tick)
  • 8.5 Clusters view is consistent across all ONOS nodes - FAIL (error)
    • ONOS nodes have different views of clusters
  • PASS (tick)
  • 8.6 There is only one SCC - FAIL (error)
  • ONOS shows 2 SCCs
  • PASS (tick)
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - FAIL (error)
    • Links are incorrect
  • PASS (tick)
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - PASS (tick)

...

  • 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 - FAIL (error)
    • ONOS nodes have different views of switch roles
  • 7.4 Get the intents from each controller - PASS (tick)
  • 7.5 Check for consistency in Intents from each controller - PASS (tick)FAIL (error)
    • ONOS nodes have different views of intents
  • 7.6 Compare current intents with intents before the failure - PASS (tick)
  • 7.7 Get the OF Table entries and compare to before component failure - PASS (tick)
  • 7.8 Leadership Election is still functional - PASS (tick)

...

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

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

Compare topology objects between Mininet and ONOS

...

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

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

Compare topology objects between Mininet and ONOS

...

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

...

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

...