Versions Compared

Key

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

...

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

commit 03ae0acdd8c1b778391c13093038b2e36bd183b2 dc897a64d6bcd4a94a6c7431aca1a8a096b4e8d6 (HEAD -] master, origin/master, origin/HEAD)
Author: Carmelo Cascone [carmelo@opennetworking.org柯志勇10068695 [ke.zhiyong@zte.com.cn]
AuthorDate: Thu Fri Oct 11 0819 17:3133:59 17 2018 -0700+0800
Commit: Carmelo Cascone Ray Milkey [carmelo@opennetworkingray@opennetworking.org]
CommitDate: Thu Fri Oct 18 2219 14:3053:46 2018 +0000
Bump version of P4Runtime to 1.0.0rc3 and P4 tools
If path is empty but not null, The following code may be error.

Case 1: Starting up 7 node(s) ONOS cluster - PASS

...

  • 8.1 Comparing ONOS topology to MN topology - 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 - PASS (tick)
  • 8.6 There is only one SCC - PASS (tick)
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - PASS (tick)

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

...

FAIL

  • 5.1 Check that each switch has a master - PASS (tick)
  • 5.2 Get the Mastership of each switch from each controller - No Result (warning)
  • 5.3 Read device roles from ONOS - PASS (tick)
  • 5.4 Check for consistency in roles from each controller - PASS (tick)FAIL (error)
    • ONOS nodes have different views of switch roles
  • 5.5 Get the intents from each controller - PASS (tick)
  • 5.6 Check for consistency in Intents from each controller - PASS (tick)
  • 5.7 Get the flows from each controller - PASS (tick)
  • 5.8 Check for consistency in Flows from each controller - PASS (tick)
  • 5.9 Get the OF Table entries - No Result (warning)
  • 5.10 Start continuous pings - No Result (warning)
  • 5.11 Collecting topology information from ONOS - No Result (warning)
  • 5.12 Host view is consistent across ONOS nodes - PASS (tick)
  • 5.13 Each host has an IP address - PASS (tick)
  • 5.14 Cluster view is consistent across ONOS nodes - PASS (tick)
  • 5.15 Cluster view correct across ONOS nodes - PASS (tick)
  • 5.16 Comparing ONOS topology to MN - PASS (tick)
  • 5.17 Device information is correct - PASS (tick)
  • 5.18 Links are correct - PASS (tick)
  • 5.19 Hosts are correct - PASS (tick)

...

  • 8.1 Comparing ONOS topology to MN topology - 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 - PASS (tick)
  • 8.6 There is only one SCC - PASS (tick)
  • 8.7 Device information is correct - PASS (tick)
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - PASS (tick)

Case 7: Running ONOS Constant State Tests -

...

PASS

  • 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
  • PASS (tick)
  • 7.4 Get the intents from each controller - PASS (tick)
  • 7.5 Check for consistency in Intents from each controller - PASS (tick)
  • 7.6 Leadership Election is still functional - PASS (tick)

...