SRDynamicConf at 12 Apr 2018 07:11:36

<img src="https://jenkins.onosproject.org/view/QA/job/postjob-Fabric3/lastSuccessfulBuild/artifact/SRDynamicConf_onos-1.12_20-builds_graph.jpg", alt="SRDynamicConf", style="width:525px;height:350px;border:0">
commit 0a8bfdd05ece7bfdb46d1097fcaaed86aa8c6995 (HEAD -] onos-1.12, origin/onos-1.12)
Author: Jordan Halterman [jordan@opennetworking.org]
AuthorDate: Tue Dec 19 14:56:08 2017 -0800
Commit: Charles Chan [charles@opennetworking.org]
CommitDate: Wed Apr 11 23:38:11 2018 +0000

[ONOS-7332] Ensure DEVICE_ADDED events are not skipped after device creation on a non-master node

Case 13: Changing port configuration from untagged 10 to tagged 10, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 23: Changing port configuration from untagged 10 to tagged 20 and native 10, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 33: Changing port configuration from untagged 10 to untagged 110, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 43: Changing port configuration from untagged 10 to tagged 20, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 53: Changing port configuration from untagged 10 to tagged 20 with native 10, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 63: Changing port configuration from untagged 10 to tagged 120 with native 110, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 73: Changing port configuration from tagged 10 to untagged 10, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 83: Changing port configuration from tagged 20 to tagged 20 and native 10, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 93: Changing port configuration from tagged 10 to tagged 120 with native 110, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 103: Changing port configuration from tagged 10 and native 20 to untagged 20, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 113: Changing port configuration from tagged 20 and native 10 to tagged 20, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 123: Changing port configuration from tagged 20 and native 10 to tagged 20 and native 110, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 133: Changing port configuration from tagged 20 and native 10 to tagged 120 and native 10, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 143: Changing port configuration from untagged 10 to tagged 20, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 153: Changing port configuration from untagged 10 to tagged 120, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 163: Changing port configuration from untagged 10 to tagged 20 and native 10, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 173: Changing port configuration from tagged 20 to tagged 120, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 183: Changing port configuration from tagged 20 to tagged 20 and native 10, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 193: Changing port configuration from tagged 20 and native 10 to untagged 20, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 203: Changing port configuration from tagged 20 and native 10 to tagged 20, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 213: Changing port configuration from tagged 20 and native 10 to tagged 20 and native 110, with 2x2 leaf-spine topology and 3 ONOS instances - PASS

Case 223: Changing port configuration from tagged 20 and native 10 to tagged 120 and native 10, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 233: Consecutive configuration changes, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL

Case 243: Changing port configuration from 10.0.2.254/24 to 10.0.6.254/24, with 2x2 leaf-spine topology and 3 ONOS instances - FAIL