Bug 1618788
| Summary: | [OSP-13] Fix for vhost-user backend crash on SET_MEM_TABLE request handling while port enabled | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | atelang <atelang> | |
| Component: | openvswitch | Assignee: | Maxime Coquelin <maxime.coquelin> | |
| Status: | CLOSED ERRATA | QA Contact: | Roee Agiman <ragiman> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 13.0 (Queens) | CC: | apevec, aschultz, atelang, cfontain, chrisw, dbecker, dcadzow, fbaudin, fleitner, jschluet, lhh, markmc, mburns, morazi, ovs-team, rheslop, rhos-maint, slinaber, srevivo, yrachman | |
| Target Milestone: | async | Keywords: | Triaged, ZStream | |
| Target Release: | 13.0 (Queens) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openvswitch-2.9.0-56.el7fdp | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, an OVS-DPDK segfault would occur after an instance reboot or after initializing its networking interfaces. This was caused by a regression introduced by OVS 2.9 and occured with VMs having one or more OVS-DPDK ports and SR-IOV virtual functions. After this fix, OVS-DPDK will not longer segfault under these conditions.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1618791 (view as bug list) | Environment: | ||
| Last Closed: | 2018-09-17 16:46: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: | ||||
| Bug Depends On: | 1618488 | |||
| Bug Blocks: | 1618791 | |||
|
Description
atelang
2018-08-17 15:12:08 UTC
Further information from Franck - this is a regression introduced by OVS 2.9 which causes a segfault when booting a VM with at least one OVS-DPDK port and one SRI-OV VF 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:2719 Done - bugzilla 1678351 is created, thanks! |