SRDynamicConf at 08 Feb 2019 11:22:53

<img src="https://jenkins.onosproject.org/view/QA/job/postjob-Fabric3/lastSuccessfulBuild/artifact/SRDynamicConf_onos-2.0_20-builds_graph.jpg", alt="SRDynamicConf", style="width:525px;height:350px;border:0">
commit 894ff117f741c735697632a070e0185cb65dc491 (HEAD -] onos-2.0, origin/onos-2.0)
Author: Carmelo Cascone [carmelo@opennetworking.org]
AuthorDate: Wed Feb 6 17:23:05 2019 -0800
Commit: Carmelo Cascone [carmelo@opennetworking.org]
CommitDate: Thu Feb 7 20:00:50 2019 +0000

Set all write responses as failed when P4Runtime server returns error
--
(cherry picked from commit b203b648185d88868a05567203597c8c0dead092)

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

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

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

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

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