[BGPCEP-289] Metadata not available for modification NodeModification Created: 16/Oct/15 Updated: 03/Mar/19 Resolved: 03/May/16 |
|
| Status: | Resolved |
| Project: | bgpcep |
| Component/s: | BGP |
| Affects Version/s: | Bugzilla Migration |
| Fix Version/s: | Bugzilla Migration |
| Type: | Bug | ||
| Reporter: | Vratko Polak | Assignee: | Milos Fabian |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| External issue ID: | 4488 |
| Description |
|
This may be a bug in yangtools or md-sal or clustering, but similar When trying to connect 600 BGP peers (each with one route to advertise), the exception below appears in karaf.log (I will try to reproduce with more verbose logging). This appears both on Lithium-SR1 and on recent Lithium snapshot builds. The suite fails due to bugs in test code, so it is currently unknown what consequences the exception has on BGP functionality. 2015-10-16 10:05:57,293 | ERROR | ult-dispatcher-2 | Dispatcher | 177 - com.typesafe.akka.slf4j - 2.3.10 | Metadata not available for modification NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)peer[ {(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)peer-id=bgp://127.0.0.150}], modificationType=TOUCH, childModification={(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)effective-rib-in=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)effective-rib-in, modificationType=TOUCH, childModification={(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)tables=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)tables, modificationType=TOUCH, childModification={(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)tables[ {(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)afi=(urn:opendaylight:params:xml:ns:yang:bgp-types?revision=2013-09-19)ipv4-address-family, (urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)safi=(urn:opendaylight:params:xml:ns:yang:bgp-types?revision=2013-09-19)unicast-subsequent-address-family}]=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)tables[ {(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)afi=(urn:opendaylight:params:xml:ns:yang:bgp-types?revision=2013-09-19)ipv4-address-family, (urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)safi=(urn:opendaylight:params:xml:ns:yang:bgp-types?revision=2013-09-19)unicast-subsequent-address-family}], modificationType=WRITE, childModification={(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)attributes=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)attributes, modificationType=WRITE, childModification={}], (urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)routes=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)routes, modificationType=WRITE, childModification={}], (urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)afi=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)afi, modificationType=WRITE, childModification={}], (urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)safi=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)safi, modificationType=WRITE, childModification={}]}]}]}]}] ], modificationType=TOUCH, childModification={(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)effective-rib-in=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)effective-rib-in, modificationType=TOUCH, childModification={(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)tables=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)tables, modificationType=TOUCH, childModification={(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)tables[ {(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)afi=(urn:opendaylight:params:xml:ns:yang:bgp-types?revision=2013-09-19)ipv4-address-family, (urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)safi=(urn:opendaylight:params:xml:ns:yang:bgp-types?revision=2013-09-19)unicast-subsequent-address-family}]=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)tables[ {(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)afi=(urn:opendaylight:params:xml:ns:yang:bgp-types?revision=2013-09-19)ipv4-address-family, (urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)safi=(urn:opendaylight:params:xml:ns:yang:bgp-types?revision=2013-09-19)unicast-subsequent-address-family}], modificationType=WRITE, childModification={(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)attributes=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)attributes, modificationType=WRITE, childModification={}], (urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)routes=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)routes, modificationType=WRITE, childModification={}], (urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)afi=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)afi, modificationType=WRITE, childModification={}], (urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)safi=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)safi, modificationType=WRITE, childModification={}]}]}]}]}] |
| Comments |
| Comment by Vratko Polak [ 16/Oct/15 ] |
|
Attached DEBUG log. Too convoluted for me to track the affected thread(s), but the exception is there. |
| Comment by Vratko Polak [ 16/Oct/15 ] |
|
Attachment karaf_20151016.log.tar.xz has been added with description: tar.xz archive of karaf.log at DEBUG verbosity |
| Comment by Claudio David Gasparini [ 04/Nov/15 ] |
|
Closing the bugs, since it has not been seen again. It may had been cause of another application and it has been fixed. |
| Comment by Vratko Polak [ 16/Nov/15 ] |
|
This was a valid bug in its time, WORKSFORME is more appropriate status for bugs which "fixed themselves". |
| Comment by Vratko Polak [ 04/Feb/16 ] |
|
Today there were not many Bugs visible in CSIT job, so it became apparent this (heisen-) Bug is not fixed yet (on Beryllium). The failure happened in [0], once again is suite which uses 600 BGP peers, fairly soon in phase when BGP routes are ingested (no withdrawals). So this probably is not an issue with memory pressure, and it does not look like a duplicate of Here are the first two exceptions: 2016-02-04 09:40:53,704 | WARN | lt-dispatcher-15 | ConcurrentDOMDataBroker | 143 - org.opendaylight.controller.sal-distributed-datastore - 1.3.0.SNAPSHOT | Tx: DOM-CHAIN-4-179221 Error during phase CAN_COMMIT, starting Abort ], modificationType=TOUCH, childModification={(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)effective-rib-in=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)effective-rib-in, modificationType=TOUCH, childModification={(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)tables=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)tables, modificationType=TOUCH, childModification={(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)tables[ {(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)afi=(urn:opendaylight:params:xml:ns:yang:bgp-types?revision=2013-09-19)ipv4-address-family, (urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)safi=(urn:opendaylight:params:xml:ns:yang:bgp-types?revision=2013-09-19)unicast-subsequent-address-family}]=NodeModification [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)tables[ {(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)afi=(urn:opendaylight:params:xml:ns:yang:bgp-types?revision=2013-09-19)ipv4-address-family, (urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)safi=(urn:opendaylight:params:xml:ns:yang:bgp-types?revision=2013-09-19)unicast-subsequent-address-family}], modificationType=WRITE, childModification={}]}]}]}] |
| Comment by Robert Varga [ 04/Mar/16 ] |
|
This looks as though the peer may be flapping: [identifier=(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)peer[ {(urn:opendaylight:params:xml:ns:yang:bgp-rib?revision=2013-09-25)peer-id=bgp://127.0.1.44}], modificationType=TOUCH e.g. the peer has been removed while we were still adding its effective-rib-in. |
| Comment by Milos Fabian [ 11/Mar/16 ] |