Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

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 581c8407e613a27aaa573a600828b30a37066fb8 commit aec67f8d9c49a2c845b0fedb45a103f8006f5559 (HEAD, origin/master, origin/HEAD, master)
Author: MaheshRaju-Huawei pierventre [maheshpier@opennetworking.somalaraju@huawei.comorg]
AuthorDate: Mon Jul 18 16:39:25 2016 +0530
Commit: Gerrit Code Review [gerrit@onlab.usThu Sep 23 19:03:14 2021 +0200
Commit: Pier Luigi Ventre [pier@opennetworking.org]
CommitDate: Tue Jul Mon Sep 27 19 08:0227:29 2016 55 2021 +0000
PCE WEB GUI defect Fixes
[ONOS-4811,ONOS-4812, ONOS-4813]
HTML

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

Case 1: Setting up test environment - PASS

Setup the test environment including installing ONOS, starting Mininet and ONOScli sessions.

SDFAB-616] Inconsistent format of port number in DhcpRelay
--
(cherry picked from commit 61bd673eec2282aff175daff141059870db78c7d)

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

For loading from params file, and pull and build the latest ONOS package

  • 1.1 Constructing test variables - PASS (tick)
  • 1.2 Apply cell to environment - PASS (tick)
  • 1.3 Uninstalling Atomix
  • 1.1 Create cell file - No Result (warning)
  • 1.2 Applying cell variable to environment - No Result (warning)
  • 1.3 Starting Mininet - PASS (tick)
  • 1.4 Git checkout and pull master - No Result (warning)Uninstalling ONOS package - PASS (tick)
  • 1.5 Using mvn clean install Starting Mininet - PASS (tick)
  • 1.6 Creating ONOS package - PASS (tick)
  • 1.7 Installing Atomix - PASS (tick)
  • 1.8 Installing ONOS package - PASS (tick)
  • 1.9 Set up ONOS secure SSH - PASS (tick)
  • 1.8 10 Checking if ONOS is up yet service - PASS (tick)
  • 1.9 11 Starting ONOS CLI sessions - PASS (tick)
  • 1.12 Checking ONOS nodes - PASS (tick)
  • 1.13 Checking ONOS applications - PASS (tick)
  • 1.10 14 Checking ONOS nodes - PASS (tick)
  • 1.11 15 Activate apps defined in the params file - No Result (warning)
  • 1.12 16 Set ONOS configurations - PASS (tick)
  • 1.17 Check app ids - PASS (tick)
  • 1.13 App Ids check 18 Set logging levels - 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 -

...

FAIL

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN topology - PASS (tick)FAIL (error)
    • ONOS topology don't match Mininet
  • 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)FAIL (error)
    • ONOS nodes have different views of clusters
  • 8.6 There is only one SCC - PASS (tick)
  • 8.7 Device information is correct - PASS (tick)FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 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 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 ) - 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 - FAIL (error)
    • Error looking up host ids
  • 3.7 Intent Anti-Entropy dispersion - PASS (tick)

Case 4: Verify connectivity by sending traffic across Intents - FAIL

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

  • 4.1 Check Intent state - PASS (tick)
  • 4.2 Ping across added host intents - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • 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.

Case

...

8

...

  • ONOS nodes have different views of clusters

...

  • Device information is incorrect

...

:

...

  • 14.1 Install leadership election app - PASS (tick)
  • 14.2 Run for election on each node - PASS (tick)
  • 14.3 First node was elected leader - PASS (tick)

Case 16: Install Primitives app - PASS

  • 16.1 Install Primitives app - PASS (tick)

Case 17: Check for basic functionality with distributed primitives - FAIL

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

  • 17.1 Increment then get a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.2 Get then Increment a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.3 Counters we added have the correct values - FAIL (error)
    • Added counters are incorrect
  • 17.4 Add -8 to then get a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.5 Add 5 to then get a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.6 Get then add 5 to a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.7 Counters we added have the correct values - FAIL (error)
    • Added counters are incorrect
  • 17.8 Distributed Set get - FAIL (error)
    • Set elements are incorrect
  • 17.9 Distributed Set size - FAIL (error)
    • Set sizes are incorrect
  • 17.10 Distributed Set add() - FAIL (error)
    • Set add was incorrect
  • 17.11 Distributed Set addAll() - FAIL (error)
    • Set addAll was incorrect
  • 17.12 Distributed Set contains() - FAIL (error)
    • Set contains failed
  • 17.13 Distributed Set containsAll() - PASS (tick)
  • 17.14 Distributed Set remove() - FAIL (error)
    • Set remove was incorrect
  • 17.15 Distributed Set removeAll() - FAIL (error)
    • Set removeAll was incorrect
  • 17.16 Distributed Set addAll() - FAIL (error)
    • Set addAll was incorrect
  • 17.17 Distributed Set clear() - FAIL (error)
    • Set clear was incorrect
  • 17.18 Distributed Set addAll() - FAIL (error)
    • Set addAll was incorrect
  • 17.19 Distributed Set retain() - FAIL (error)
    • Set retain was incorrect
  • 17.20 Partitioned Transactional maps put - PASS (tick)
  • 17.21 Partitioned Transactional maps get - FAIL (error)
    • Partitioned Transactional Map values incorrect

Case 61: Partition ONOS nodes into two distinct partitions - PASS

  • 61.1 Checking ONOS Logs for errors - No Result (warning)
  • 61.2 Partitioning ONOS nodes - PASS (tick)
  • 61.3 Sleeping 60 seconds - No Result (warning)

...

Compare ONOS Topology view to Mininet topology - FAIL

Compare topology objects between Mininet and ONOS

  • 8.1 Comparing ONOS topology to MN topology - FAIL (error)
    • ONOS topology don't match Mininet
  • 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
  • 8.6 There is only one SCC - FAIL (error)
    • ONOS shows 5 SCCs
  • PASS (tick)
  • 8.7 Device information is correct - FAIL (error)
    • Device information is incorrect
  • 8.8 Links are correct - PASS (tick)
  • 8.9 Hosts are correct - PASS (tick)
  • 8.10 Checking ONOS nodes - PASS (tick)

Case

...

3

...

  • ONOS nodes have different views of intents

...

  • Changes were found in the flow tables

...

  • Something went wrong with Leadership election

Case 4: Verify connectivity by sending traffic across Intents - FAIL

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

  • 4.1 Check Intent state - FAIL (error)
    • Intents are not all in INSTALLED state
  • 4.2 Ping across added host intents - FAIL (error)
    • Intents have not been installed correctly, pings failed.
  • 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.

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

  • 15.1 Run for election on each node - PASS (tick)
  • 15.2 Check that each node shows the same leader and candidates - PASS (tick)
  • 15.3 Find current leader and withdraw - PASS (tick)
  • 15.4 Check that a new node was elected leader - PASS (tick)
  • 15.5 Check that that new leader was the candidate of old leader - PASS (tick)
  • 15.6 Run for election on old leader( just so everyone is in the hat ) - PASS (tick)
  • 15.7 Check that oldLeader is a candidate, and leader if only 1 node - PASS (tick)

Case 17: Check for basic functionality with distributed primitives - FAIL

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

  • 17.1 Increment then get a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.2 Get then Increment a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.3 Counters we added have the correct values - FAIL (error)
    • Added counters are incorrect
  • 17.4 Add -8 to then get a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.5 Add 5 to then get a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.6 Get then add 5 to a default counter on each node - FAIL (error)
    • Error incrementing default counter
  • 17.7 Counters we added have the correct values - FAIL (error)
    • Added counters are incorrect
  • 17.8 Distributed Set get - PASS (tick)
  • 17.9 Distributed Set size - PASS (tick)
  • 17.10 Distributed Set add() - PASS (tick)
  • 17.11 Distributed Set addAll() - PASS (tick)
  • 17.12 Distributed Set contains() - PASS (tick)
  • 17.13 Distributed Set containsAll() - PASS (tick)
  • 17.14 Distributed Set remove() - PASS (tick)
  • 17.15 Distributed Set removeAll() - PASS (tick)
  • 17.16 Distributed Set addAll() - PASS (tick)
  • 17.17 Distributed Set clear() - PASS (tick)
  • 17.18 Distributed Set addAll() - PASS (tick)
  • 17.19 Distributed Set retain() - PASS (tick)
  • 17.20 Partitioned Transactional maps put - PASS (tick)
  • 17.21 Partitioned Transactional maps get - PASS (tick)

Case 62: Healing Partition - PASS

  • 62.1 Deleteing firewall rules - PASS (tick)

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

...

  • ONOS topology don't match Mininet

...

  • ONOS nodes have different views of hosts

...

  • Host information is incorrect

...

: Adding host Intents - FAIL