[OPNFLWPLUG-444] flow capable stats are not in operational store Created: 18/May/15  Updated: 27/Sep/21  Resolved: 26/May/15

Status: Resolved
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Jamo Luhrsen Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 3261

 Description   

This bug is to track failures in CI.

https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-1node-cds-flow-services-all-master/

some test cases are looking for the presence of the string "flow-capable-node-connector-statistics" for a specific
node. It does not exist.

the log has one message that might be related:

2015-05-18 14:33:54,359 | WARN | CommitFutures-2 | StatisticsManagerImpl | 173 - org.opendaylight.openflowplugin.applications.statistics-manager - 0.1.0.SNAPSHOT | Failed to export Flow Capable Statistics, Transaction DOM-CHAIN-2-31 failed.
TransactionCommitFailedException

{message=canCommit encountered an unexpected failure, errorList=[RpcError [message=canCommit encountered an unexpected failure, severity=ERROR, errorType=APPLICATION, tag=operation-failed, applicationTag=null, info=null, cause=org.opendaylight.yangtools.yang.data.api.schema.tree.ConflictingModificationAppliedException: Node was deleted by other transaction.]]}

This started happening for the test job #429 which was triggered by this gerrit patch:
https://git.opendaylight.org/gerrit/#/c/20173/

Even though that was the OFP change that triggered the test job, it's possible that other projects
had made changes in between that made it in to the distribution that first saw the failures.



 Comments   
Comment by Jozef Behran [ 26/May/15 ]

Could you please supply stacktrace as well? This seems very similar to another problem I am experiencing with BGP and which is described as CONTROLLER-1337.

Comment by Jamo Luhrsen [ 26/May/15 ]

This is no longer seen in CI.

Comment by Jamo Luhrsen [ 26/May/15 ]

(In reply to Jozef Behran from comment #1)
> Could you please supply stacktrace as well? This seems very similar to
> another problem I am experiencing with BGP and which is described as bug
> #3372.

Jozef,

if you need me to get a stacktrace still, I can probably dig up an older distro that was seeing this. let me know if it's needed.

Thanks,
JamO

Generated at Wed Feb 07 20:32:30 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.