Bug 1586169
| Summary: | [Infra] NPE seen at org.opendaylight.netvirt.fibmanager.FibRpcServiceImpl.createFibEntry | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Tim Rozet <trozet> |
| Component: | opendaylight | Assignee: | Josh Hershberg <jhershbe> |
| Status: | CLOSED ERRATA | QA Contact: | Tomas Jamrisko <tjamrisk> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 13.0 (Queens) | CC: | aadam, jchhatba, jhershbe, lmarsh, mkolesni, nmanos, nyechiel, tjamrisk, trozet, vorburger |
| Target Milestone: | z1 | Keywords: | Triaged, ZStream |
| Target Release: | 13.0 (Queens) | Flags: | trozet:
needinfo-
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | Infra | ||
| Fixed In Version: | opendaylight-8.3.0-1.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Missing parameters from createFibEntry generate a Null Pointer Exception (NPE) during NAT setup. This bug may result in missing FIB entries from the routing table, causing NAT or routing to fail. This update adds the proper parameters to the RPC call. NPE is no longer seen in the OpenDaylight log, and NAT and routing function correctly.
|
Story Points: | --- |
| Clone Of: | Environment: |
N/A
|
|
| Last Closed: | 2018-07-19 13:53:05 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Tim Rozet
2018-06-05 16:01:10 UTC
Upstream NETVIRT-1133 seems to be the same, but was closed with Cannot Reproduce. Let's open that one if we have a reliable way to reproduce it here? Yeah I saw it again last night after running OOO update. What OOO update do? Does it delete neutron resources ? No, it restarts each ODL sequentially and updates it to a newer version. I'm not 100% certain it is the same NPE, but I saw an NPE in Fib and figured it was the same one was I was glancing through the logs post update. I think there were 2 nova instances at the time which had FIP associated with them before update. We can try to reproduce. No, it restarts each ODL sequentially and updates it to a newer version. I'm not 100% certain it is the same NPE, but I saw an NPE in Fib and figured it was the same one was I was glancing through the logs post update. I think there were 2 nova instances at the time which had FIP associated with them before update. We can try to reproduce. Gerrit patches posted upstream. see attachments I don't see this exception in karaf logs with opendaylight-8.3.0-1.el7ost.noarch. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2215 |