|
Please take a look at this log messages in attached log20160316.zip. During last testing on stable/beryllium I saw node in operational inventory on disconnected network after that not all flows were reconciled.
2016-03-16 18:42:04,174 | WARN | pool-33-thread-1 | RpcContextImpl | 157 - org.opendaylight.openflowplugin.impl - 0.2.1.SNAPSHOT | Xid cannot be reserved for new RequestContext, node:Uri [_value=openflow:18087942711149584731]
2
org.opendaylight.yangtools.yang.data.api.schema.tree.ModifiedNodeDoesNotExistException: Node /(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[
{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:18088224186126241907}
]/AugmentationIdentifier
{childNames=[(urn:opendaylight:flow:inventory?revision=2013-08-19)supported-match-types, (urn:opendaylight:flow:inventory?revision=2013-08-19)port-number, (urn:opendaylight:flow:inventory?revision=2013-08-19)serial-number, (urn:opendaylight:flow:inventory?revision=2013-08-19)group, (urn:opendaylight:flow:inventory?revision=2013-08-19)ip-address, (urn:opendaylight:flow:inventory?revision=2013-08-19)manufacturer, (urn:opendaylight:flow:inventory?revision=2013-08-19)stale-group, (urn:opendaylight:flow:inventory?revision=2013-08-19)supported-instructions, (urn:opendaylight:flow:inventory?revision=2013-08-19)supported-actions, (urn:opendaylight:flow:inventory?revision=2013-08-19)table, (urn:opendaylight:flow:inventory?revision=2013-08-19)stale-meter, (urn:opendaylight:flow:inventory?revision=2013-08-19)hardware, (urn:opendaylight:flow:inventory?revision=2013-08-19)switch-features, (urn:opendaylight:flow:inventory?revision=2013-08-19)description, (urn:opendaylight:flow:inventory?revision=2013-08-19)software, (urn:opendaylight:flow:inventory?revision=2013-08-19)meter]}
/(urn:opendaylight:flow:inventory?revision=2013-08-19)group/group[
{(urn:opendaylight:flow:inventory?revision=2013-08-19)group-id=3}
] does not exist. Cannot apply modification to its children.
|
|
A patch for this bug was submitted:
https://git.opendaylight.org/gerrit/#/c/38369/
https://git.opendaylight.org/gerrit/#/c/38111/
https://git.opendaylight.org/gerrit/#/c/37661/
To better assess the impact of this bug and fix, could someone from your team please help us identify the following:
Severity: Could you elaborate on the severity of this bug? Is this a BLOCKER such that we cannot release Beryllium without it? Is there a workaround such that we can write a release note and fix in future Beryllium SR3?
Testing: Could you also elaborate on the testing or this patch? How extensively has this patch been tested? Is it covered by any unit tests or system tests?
Impact: Does this fix impact any dependent projects?
|
|
This patch was made behalf on clustering changes needed to be implemented.On the changes were made and merged before the release SR2, we tested it in cluster in our place. Changes priorities were to be stable on connection flapping, and we rewrote whole connection and disconnection logic, made double candidate approach in plugin. Three patches mentioned, took to long to test, we manage better testing on cluster as we were able before, so we made a step forward. This patches meant to be ready before SR2 and merged before the lock. We all, most of us, agreed it is a regression for the SR2 in “cluster environment”. I don’t think we are able to make any workaround, its too complex to simplify this patch.
We were testing in on our cluster every day for last two weeks. But we don’t have any robot tests, integration tests, but some unit test.
This fix doesn’t impact any depending project, it is changing only plugin in cluster behavior like change mastership. It isn’t change statistics gathering nor rpc services nor yang models.
Patches were already merged in beryllium, I will close this bug, if some errors or bug comes out from testing we should raise another bug.
|
log20160316.zip