odl1_karaf.log.tar.xz
[NETVIRT-486] networks Add received exception; Config store updated; undo with Delete if needed. Created: 20/Feb/17 Updated: 01/Mar/17 Resolved: 01/Mar/17 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | General |
| Affects Version/s: | Boron |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Sam Hague | Assignee: | Kiran N Upadhyaya |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
odl1_karaf.log.tar.xz
|
| External issue ID: | 7831 |
| Description |
|
Many BgpConfigurationManager exceptions but bgp is not in use.
|
| Comments |
| Comment by Hanamantagoud V Kandagal [ 21/Feb/17 ] |
|
Hi Sam , Could you please let me know what are the exceptions you see in BgpConfigurationManager ? |
| Comment by Hanamantagoud V Kandagal [ 21/Feb/17 ] |
|
Hi Sam , Could you please let me know what are the exceptions you see in BgpConfigurationManager ? |
| Comment by Sam Hague [ 21/Feb/17 ] |
|
Attachment odl1_karaf.log.tar.xz has been added with description: karaf log for job 139 |
| Comment by Sam Hague [ 21/Feb/17 ] |
|
(In reply to Sam Hague from comment #3) There are many logs like the one below. The one below is for networks and the Add operation, but it happens for other types and operations. I think in all cases the log comes out because thrift/bgp is not setup (which is expected) but the bgp code is receiving events. I think in all cases it is because the bgpclient is null but there is a bgprouter instance. So you get down into the dispatch based on having a bgprouter and then the bgpclient in null so it punts. There probably should be an earlier check for the client or maybe the bgprouter check should also have a check for the client. The other issue is that I don't understand why bgp is even receiving events. Seems like only if a bgp router or object was really in use should events be sent to bgp. networks Add received exception; Config store updated; undo with Delete if needed. |
| Comment by Hanamantagoud V Kandagal [ 26/Feb/17 ] |
|
From my analysis , i have figured out that due to code refactoring in VpnInterfaceManager for EVPN feature, check for (rd=null) when subnet is added to router is missing . Hence routes are getting published even though BGPVPN is not created. |
| Comment by Kiran N Upadhyaya [ 27/Feb/17 ] |
|
Review link https://git.opendaylight.org/gerrit/#/c/52287/ |