SRDynamicConf at 02 Apr 2021 22:14:58

<img src="https://jenkins.onosproject.org/view/QA/job/postjob-Fabric4/lastSuccessfulBuild/artifact/SRDynamicConf-stratum_master_20-builds_graph.jpg", alt="SRDynamicConf-stratum", style="width:525px;height:350px;border:0">
commit 2b4de873e4033b7973b399d25cb8828a73bc2e24 (HEAD -] master, origin/master, origin/HEAD)
Author: Thomas Vachuska [tom@opennetworking.org]
AuthorDate: Tue Mar 30 16:31:34 2021 -0700
Commit: Charles Chan [charles@opennetworking.org]
CommitDate: Fri Apr 2 07:12:47 2021 +0000

Added mechanism for apps to easily add their own custom link/node/host highlighting wihout having to create a new UI extensions

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

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

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 - FAIL

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

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

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

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 - FAIL

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

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 - FAIL

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

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

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

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 - FAIL

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

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

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 - FAIL

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