Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1129377

Summary: Vdsm sampling threads unexpectingly stops with IOError ENODEV
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: vdsmAssignee: Antoni Segura Puimedon <asegurap>
Status: CLOSED ERRATA QA Contact: Martin Pavlik <mpavlik>
Severity: high Docs Contact:
Priority: high    
Version: 3.4.0CC: adahms, akotov, asegurap, bazulay, danken, dossow, ecohen, fromani, iheim, jcoscia, jentrena, juwu, lpeer, luvilla, mkalinin, mtessun, myakove, nyechiel, oourfali, pablo.iranzo, pdwyer, tdosek, yeylon
Target Milestone: ---Keywords: ZStream
Target Release: 3.4.3   
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: 4.14.17-1 Doc Type: Bug Fix
Doc Text:
Previously, the VDSM statistics gathering thread did not account for network devices being removed while an instance of statistics gathering was in progress. This would result in attempting to retrieve data from a non-existing device, causing an exception. Now, devices that are removed are also removed from the statistics report, allowing statistics gathering to return successfully even when network devices are removed while statistics gathering is in progress.
Story Points: ---
Clone Of: 1113948 Environment:
Last Closed: 2014-10-27 22:36:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1113948    
Bug Blocks: 1126430    

Comment 5 lpeer 2014-09-15 07:31:33 UTC
I support dan's comment. we can provide this as a hotfix.

Comment 8 Meni Yakove 2014-10-02 08:10:32 UTC
vdsm-4.14.13-2.el6ev.x86_64

Comment 9 Julie 2014-10-23 08:51:23 UTC
Hi Antoni,
   Please provide the doc text or set require_doc_text flag to -.

Many thanks,
Julie

Comment 11 errata-xmlrpc 2014-10-27 22:36:54 UTC
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://rhn.redhat.com/errata/RHBA-2014-1721.html