Page History

...

<img src="https://jenkins.onosproject.org/view/QA/job/postjob-VM/lastSuccessfulBuild/artifact/HAbackupRecover_unexpected ONOS branchonos-2.2_20-builds_graph.jpg", alt="HAbackupRecover", style="width:525px;height:350px;border:0">

commit 57f7828a52d85f36fb3cfb0c630e0cf66558028b f198430fee8d188a8704f0cc06f403f10df70c3a (HEAD, review/andrea_campanella/ports-updateorigin/onos-2.2, onos-2.2)
Author: Andrea Campanella [andrea@opennetworking.org]
AuthorDate: Mon Aug 10 18:06:42 2020 +0200
Commit: Andrea Campanella [andrea@opennetworking.org]
CommitDate: Mon Wed Aug 10 2212 06:4147:27 09 2020 +02000000

Ports and port description are not cleared up properly upon removal

...

• 8.1 Comparing ONOS topology to MN topology - PASS
• 8.2 Hosts view is consistent across all ONOS nodes - PASS
• 8.3 Hosts information is correct - PASS
• 8.4 Host attachment points to the network - PASS
• 8.5 Clusters view is consistent across all ONOS nodes - PASS
• 8.6 There is only one SCC - PASS
• 8.7 Device information is correct - PASS
• 8.8 Links are correct - PASS
• 8.9 Hosts are correct - PASS
• 8.10 Checking ONOS nodes - PASS

Case 21: Assigning Controller roles for switches -

...

FAIL

Check that ONOS is connected to each device. Then manually assign mastership to specific ONOS nodes using 'device-role'

• 21.1 Assign mastership of switches to specific controllers - PASS
• 21.2 Check mastership was correctly assigned - PASS FAIL
• Switches were not successfully reassigned

Case 3: Adding host Intents - PASS

...