[NETVIRT-1664] exceptions seen during L3VPN disassociation and again association. Created: 23/Jan/20 Updated: 17/Jul/20 Resolved: 17/Jul/20 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | bgpmanager |
| Affects Version/s: | Sodium |
| Fix Version/s: | Magnesium, Aluminium |
| Type: | Bug | Priority: | Medium |
| Reporter: | Srinivas Rachakonda | Assignee: | Karthikeyan Krishnan |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Logs:
karaf Logs:
Karaf exceptions: 2020-01-20T10:05:29,664 | INFO | epollEventLoopGroup-9-2 | GuardedContextImpl | 421 - org.opendaylight.openflowplugin.impl - 0.9.2 | Terminating RpcContextImpl[TERMINATED] service for node openflow:268362736803140
|
| Comments |
| Comment by Manjunath Gowda [ 23/Jan/20 ] |
|
As discussed, I tried to reproduce the issue on my local set-up, when I tried to add a vrf which is not related to any VPN, then I observed below error message, 2020-01-22T12:15:23,522 | ERROR | org.opendaylight.yang.gen.v1.urn.ericsson.params.xml.ns.yang.ebgp.rev150901.bgp.networkscontainer.Networks_AsyncDataTreeChangeListenerBase-DataTreeChangeHandler-0 | BgpConfigurationManager | networks Delete received exception;Config store updated; undo with Add if needed. org.apache.thrift.TApplicationException: BGP RD 200:1 not configured for iidKeyedInstanceIdentifier {targetType=interface org.opendaylight.yang.gen.v1.urn.ericsson.params.xml.ns.yang.ebgp.rev150901.bgp.networkscontainer.Networks, path=[org.opendaylight.yang.gen.v1.urn.ericsson.params.xml.ns.yang.ebgp.rev150901.Bgp, org.opendaylight.yang.gen.v1.urn.ericsson.params.xml.ns.yang.ebgp.rev150901.bgp.NetworksContainer, org.opendaylight.yang.gen.v1.urn.ericsson.params.xml.ns.yang.ebgp.rev150901.bgp.networkscontainer.Networks[key=NetworksKey [_rd=200:1, _prefixLen=9.9.9.10/32]]]}and val Networks{getBgpControlPlaneType=PROTOCOLL3VPN, getEncapType=GRE, getEthtag=0, getLabel=10000, getNexthop=IpAddress [_ipv4Address=Ipv4Address [_value=1.1.1.1]], getPrefixLen=9.9.9.10/32, getRd=200:1, augmentations={}}
I am trying to relate this observation with your issue.
The disassociation of vpn from network and re asscociation of the same immediately causing an issue could be due to timing/data. This issue definitely requires VPN team also need to investigate. Since calling below use cases purely from neutron VPN code base , i.e, Create L3 VPN Associate L3 VPN Dis associate L3 VPN
|
| Comment by Karthikeyan Krishnan [ 17/Jul/20 ] |
|
Reported issue is not observed in latest Magnesium and Aluminium releases. |