Page History

...

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

commit 86741ece0495abaff55e34823370b91886df55d1 8b17e0eec5332f6db915af95ee8ff271848642b7 (HEAD, origin/master, origin/HEAD, master)
Author: Jordan Halterman [jordan@opennetworking.org]
AuthorDate: Mon Tue Dec 10 1118 13:0257:31 36 2018 -0800
Commit: Jordan Halterman Ray Milkey [jordan@opennetworkingray@opennetworking.org]
CommitDate: Wed Tue Dec 12 0018 22:1650:07 15 2018 +0000
Ensure master is excluded from backups list when reading role info from mastership service
Upgrade to Atomix 3.1.0-rc2

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 - FAIL
Not all Intents in installed state
• PASS
• 100.28 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

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

• PASS
• 100.29 Kill link between s5 and h5 200.1 Delete s5. - PASS
• 200 100.2 30 Check intent states - FAIL
• Not all Intents in installed state
• 200 100.3 31 Testing connectivity... - FAIL
• Connectivity failed.
• PASS
• 100.32 Re-adding link between s5 and h5 200.4 Add s5. - PASS
• 200.5 Reconnecting links on s5 100.33 Discover h5 using ping. - No Result
• 200 100.6 34 Check intent states - FAIL
• Not all Intents in installed state
• 200.7 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

Case 300: Stop one ONOS node at a time and test connectivity. - FAIL

• PASS
• 100.35 Testing connectivity.. 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 100.36 Kill link between s6 and h6. - PASS
• 300.4 Checking ONOS nodes. - FAIL
• Apps are NOT the same across all nodes.
• 300.5 100.37 Check intent states - FAIL
• Not all Intents in installed state
• 300 100.6 38 Testing connectivity... - FAIL
• Connectivity is NOT as expected.

Case 310: Kill one ONOS node at a time and test connectivity. - FAIL

• PASS
• 100.39 Re-adding link between s6 and h6 310.1 Killing ONOS node 1. - PASS
• 310.2 Waiting for ONOS to restart 100.40 Discover h6 using ping. - No Result
• 310 100.3 41 Check intent states - FAIL
• Not all Intents in installed state
• PASS
• 100.42 310.4 Testing connectivity... - FAIL
Connectivity is NOT as expected.
• PASS

Case

...

200: Bring down one

...

switch at a time and test

...

• Not all Intents in installed state

...

• Connectivity failed.

...

• Not all Intents in installed state

...

connectivity.

...

- FAIL

...