Page History

...

...

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

commit b53d626fb03195129c0ec0802e1f953f85dcbef8 (HEAD -] master, origin/master, origin/HEAD)
Author: pierventre [pier@opennetworking.org]
AuthorDate: Wed Sep 22 11:24:38 2021 +0200
Commit: Pier Luigi Ventre [pier@opennetworking.org]
CommitDate: Thu Sep 23 07:38:36 2021 +0000

[SDFAB-612] Cluster not ready when using recent tost master images
--
(cherry picked from commit ec0e942320ef27932b4173172055151015261d7c)

Case 1: Switch Failure test with 2x2 leaf-spine topology and 1 Onos

...

- PASS

• 1.1 Constructing test variables - PASS
• 1.2 Create and Apply cell file to environment - PASS
• 1.3 Create and Install ONOS package Uninstalling Atomix - PASS
• 1.4 Starting Uninstalling ONOS service package - PASS
• 1.5 Checking if ONOS CLI is ready Creating ONOS package - PASS
• 1.6 Starting Mininet Topology Installing Atomix - PASS
• 1.7 Check whether the flow count is bigger than 116 Installing ONOS package - PASS
• 1.8 Check whether all flow status are ADDED Set up ONOS secure SSH - PASS
• 1.9 Check IP connectivity Checking ONOS service - PASS
• 1.10 Check VLAN connectivity Starting ONOS CLI sessions - PASS
• 1.11 Kill spine101 Checking ONOS nodes - PASS
• 1.12 Check IP connectivity CASE1_Failure Checking ONOS applications - PASS
• 1.13 Check VLAN connectivity CASE1_Failure Set logging levels - PASS
• 1.14 Recovering spine101 Set ONOS configurations - PASS
• 1.15 Starting Mininet Topology - PASS
• 1.16 Check whether the flow count is bigger than >= 116 - PASS
• 1.16 17 Check whether all flow status are ADDED - PASS
• 1.17 Check IP connectivity CASE1_Recovery 18 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1 - PASS
• 1.18 Check VLAN connectivity CASE1_Recovery - PASS

Case 2: Package and start ONOS using apps:drivers,segmentrouting,openflow-base,netcfghostprovider,netcfglinksprovider - FAIL

• 2.1 Create and Apply cell file - PASS
• 2.2 Create and Install ONOS package - PASS
• 2.3 Starting ONOS service - PASS
• 2.4 Checking if ONOS CLI is ready - PASS
• 2.5 Starting Mininet Topology - PASS
• 2.6 Check whether the flow count is bigger than 350 - PASS
• 2.7 Check whether all flow status are ADDED - PASS
• 2.8 Check IP connectivity - PASS
• 2.9 Check VLAN connectivity - PASS
• 2.10 Kill spine101 - PASS
• 2.11 Check IP connectivity CASE2_Failure - FAIL
• IP connectivity failed
• 2.12 Check VLAN connectivity CASE2_Failure - PASS
• 2.13 Recovering spine101 - PASS
• 2.14 Check whether the flow count is bigger than 350 - PASS
• 2.15 Check whether all flow status are ADDED - PASS
• 2.16 Check IP connectivity CASE2_Recovery - PASS
• 2.17 Check VLAN connectivity CASE2_Recovery - PASS

Case 4: Package and start ONOS using apps:drivers,segmentrouting,openflow-base,netcfghostprovider,netcfglinksprovider - PASS

• 19 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE1 - PASS
• 1.20 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE1 - PASS
• 1.21 Kill ['spine101'] - PASS
• 1.22 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1_Failure - PASS
• 1.23 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE1_Failure - PASS
• 1.24 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE1_Failure - PASS
• 1.25 Recovering ['spine101'] - PASS
• 1.26 Check whether the flow count is >= 116 - PASS
• 1.27
• 4.1 Create and Apply cell file - PASS
• 4.2 Create and Install ONOS package - PASS
• 4.3 Starting ONOS service - PASS
• 4.4 Checking if ONOS CLI is ready - PASS
• 4.5 Starting Mininet Topology - PASS
• 4.6 Check whether the flow count is bigger than 116 - PASS
• 4.7 Check whether all flow status are ADDED - PASS
• 4.8 Check IP connectivity - PASS
• 4.9 Check VLAN connectivity - PASS
• 4.10 Kill spine101 - PASS
• 4.11 Check IP connectivity CASE3_Failure - PASS
• 4.12 Check VLAN connectivity CASE3_Failure - PASS
• 4.13 Recovering spine101 - PASS
• 4.14 Check whether the flow count is bigger than 116 - PASS
• 4.15 Check whether all flow status are ADDED - PASS 4.16 Check IP connectivity CASE3
• 1.28 Verify full connectivity for [u'h1', u'h2', u'h3', u'h4'] with tag CASE1_Recovery - PASS
• 4.17 Check VLAN connectivity CASE3 1.29 Verify full connectivity for [u'olt10', u'vsg10'] with tag CASE1_Recovery - PASS

Case 5: Package and start ONOS using apps:drivers,segmentrouting,openflow-base,netcfghostprovider,netcfglinksprovider - FAIL

• 5. 1 Create and Apply cell file - PASS
• 5.2 Create and Install ONOS package - PASS
• 5.3 Starting ONOS service - PASS
• 5.4 Checking if ONOS CLI is ready - PASS
• 5.5 Starting Mininet Topology - PASS
• 5.6 Check whether the flow count is bigger than 350 - PASS
• 5.7 Check whether all flow status are ADDED - PASS
• 5.8 Check IP connectivity - PASS
• 5.9 Check VLAN connectivity - PASS
• 5.10 Kill spine101 - PASS
• 5.11 Check IP connectivity CASE4_Failure - FAIL
• IP connectivity failed
• 5.12 Check VLAN connectivity CASE4_Failure - PASS
• 5.13 Recovering spine101 - PASS
• 5.14 Check whether the flow count is bigger than 350 - PASS
• 5.15 Check whether all flow status are ADDED - PASS
• 5.16 Check IP connectivity CASE4_Recovery - PASS
• .30 Verify full connectivity for [u'olt5', u'vsg5'] with tag CASE1_Recovery - PASS
• 1.31 Stopping Mininet - PASS
• 1.32 Copying karaf logs 5.17 Check VLAN connectivity CASE4_Recovery - PASS