View Source

VPLSfailsafe at 15 Jul 2018 20:17:11

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

commit 7edca040d67b3c1b515f7dddc1343e8820d3ece0 (HEAD, origin/onos-1.13, onos-1.13)
Author: Jordan Halterman [jordan@opennetworking.org]
AuthorDate: Wed Jul 11 09:49:15 2018 -0700
Commit: Thomas Vachuska [tom@opennetworking.org]
CommitDate: Fri Jul 13 19:22:39 2018 +0000

Ensure multimap events are published on replaceValues

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

Set up ONOS with 3 node(s) ONOS cluster

1.1 Constructing test variables - PASS
1.2 Apply cell to environment - PASS
1.3 Uninstalling ONOS package - PASS
1.4 Creating ONOS package - PASS
1.5 Installing ONOS package - PASS
1.6 Set up ONOS secure SSH - PASS
1.7 Checking ONOS service - PASS
1.8 Starting ONOS CLI sessions - PASS
1.9 Starting Mininet - PASS
1.10 Activate apps defined in the params file - No Result
1.11 Set ONOS configurations - No Result
1.12 App Ids check - PASS

Case 2: - PASS

2.1 Discover hosts using pings - No Result
2.2 Load VPLS configurations - PASS
2.3 Check VPLS configurations - PASS
2.4 Check interface configurations - PASS
2.5 Check network configurations for vpls application - PASS
2.6 Check vpls app configurations - PASS
2.7 Check connectivity - PASS
2.8 Loading vpls configuration in case any configuration was missed. - PASS

Case 50: Check connectivity before running all other tests. - PASS

50.1 Check intent states - PASS
50.2 Testing connectivity... - PASS

Case 100: Bring down one host at a time and test connectivity. - FAIL

100.1 Kill link between s1 and h1. - PASS
100.2 Check intent states - FAIL

Not all Intents in installed state

100.3 Testing connectivity... - PASS
100.4 Re-adding link between s1 and h1. - PASS
100.5 Discover h1 using ping. - No Result
100.6 Check intent states - PASS
100.7 Testing connectivity... - PASS
100.8 Kill link between s2 and h2. - PASS
100.9 Check intent states - FAIL

Not all Intents in installed state

100.10 Testing connectivity... - PASS
100.11 Re-adding link between s2 and h2. - PASS
100.12 Discover h2 using ping. - No Result
100.13 Check intent states - PASS
100.14 Testing connectivity... - PASS
100.15 Kill link between s3 and h3. - PASS
100.16 Check intent states - FAIL

Not all Intents in installed state

100.17 Testing connectivity... - PASS
100.18 Re-adding link between s3 and h3. - PASS
100.19 Discover h3 using ping. - No Result
100.20 Check intent states - PASS
100.21 Testing connectivity... - PASS
100.22 Kill link between s4 and h4. - PASS
100.23 Check intent states - FAIL

Not all Intents in installed state

100.24 Testing connectivity... - PASS
100.25 Re-adding link between s4 and h4. - PASS
100.26 Discover h4 using ping. - No Result
100.27 Check intent states - FAIL

Not all Intents in installed state

100.28 Testing connectivity... - PASS
100.29 Kill link between s5 and h5. - PASS
100.30 Check intent states - FAIL

Not all Intents in installed state

100.31 Testing connectivity... - PASS
100.32 Re-adding link between s5 and h5. - PASS
100.33 Discover h5 using ping. - No Result
100.34 Check intent states - PASS
100.35 Testing connectivity... - PASS
100.36 Kill link between s6 and h6. - PASS
100.37 Check intent states - FAIL

Not all Intents in installed state

100.38 Testing connectivity... - PASS
100.39 Re-adding link between s6 and h6. - PASS
100.40 Discover h6 using ping. - No Result
100.41 Check intent states - PASS
100.42 Testing connectivity... - PASS

Case 200: Bring down one switch at a time and test connectivity. - FAIL