Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1498155 - Hot-unplugging a vhost network device leaks references to VFIOPCIDevice's [OSP 12]
Hot-unplugging a vhost network device leaks references to VFIOPCIDevice's [OS...
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: qemu-kvm-rhev (Show other bugs)
12.0 (Pike)
x86_64 Unspecified
high Severity high
: rc
: 12.0 (Pike)
Assigned To: Virtualization Maintenance
Shai Revivo
: Triaged, ZStream
Depends On: 1490742
Blocks:
  Show dependency treegraph
 
Reported: 2017-10-03 10:58 EDT by Jason Joyce
Modified: 2018-02-05 14:15 EST (History)
23 users (show)

See Also:
Fixed In Version: qemu-kvm-rhev-2.9.0-16.el7_4.7
Doc Type: Bug Fix
Doc Text:
Hot-unplugging Virtual Function I/O (VFIO) devices previously failed when performed after hot-unplugging a vhost network device. This update fixes the underlying code, and the VFIO device is unplugged correctly in the described circumstances.
Story Points: ---
Clone Of: 1490742
Environment:
Last Closed: 2017-12-13 17:13:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Bugzilla 1371930 None None None 2017-10-03 10:58 EDT
Red Hat Product Errata RHEA-2017:3462 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-15 20:43:25 EST

  None (edit)
Comment 6 errata-xmlrpc 2017-12-13 17:13:08 EST
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/RHEA-2017:3462

Note You need to log in before you can comment on or make changes to this bug.