Page History

...

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

commit 63cb1a8da31490594dc6e8c35f93f5d7fb25d064 ab12330c351a75cfe21080d9531700146d270ab7 (HEAD -] masteronos-2.5, origin/master, origin/HEADonos-2.5)
Author: Anurag Chadha [anurag.chadha@hsc.comONOS Jenkins User [jenkins@onlab.us]
AuthorDate: Fri Nov 20 16:21:09 2020 +0530Tue Dec 1 22:36:31 2020 +0000
Commit: Anurag Chadha [anurag.chadha@hsc.comONOS Jenkins User [jenkins@onlab.us]
CommitDate: Fri Nov 20 17:58:24 2020 +0530
[ONOS-8116] Fix for retry at netconf providerTue Dec 1 22:36:31 2020 +0000

Starting snapshot 2.5.0-SNAPSHOT

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

...

• 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 - PASS
• 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.28 35 Testing connectivity... - PASS
• 100.36 Kill link between s6 and h6. - PASS
• 100.37 Check intent states - FAIL
Connectivity is NOT as expected.
• • 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

...

• 200.1 Delete s5. - PASS
• 200.2 Check intent states - FAIL
• Not all Intents in installed state
• 200.3 Testing connectivity... - FAIL
Connectivity failed.
• PASS
• 200.4 Add s5. - PASS
• 200.5 Reconnecting links on s5. - No Result
• 200.6 Check intent states - FAIL
• Not all Intents in installed state
• PASS
• 200.7 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

...

• 300.1 Stop ONOS node 0. - PASS
• 300.2 Testing connectivity... - FAIL
• Connectivity failed.
• 300.3 Restart ONOS node 0 and checking status of restart. - PASS
• 300.4 Checking ONOS nodes - FAIL
• Apps are NOT the same across all nodes.
• 300.5 Check intent states - FAIL
Not all Intents in installed state
• PASS
• 300.6 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

...

• 400.1 Bring down link: s1 to h1 - PASS
• 400.2 Check intent states - FAIL
• Not all Intents in installed state
• PASS
• 400.3 Testing connectivity... - FAIL
• Connectivity failed.
• 400.4 Adding link: s1 to h1. - PASS
• 400.5 Check intent states - FAIL
Not all Intents in installed state
• PASS
• 400.6 Testing connectivity... - FAIL
• Connectivity is NOT as expected.