Bug 1063433

Summary:	VDSM does not handle network devices that do not expose "speed"
Product:	[Retired] oVirt	Reporter:	Trey Dockendorf <treydock>
Component:	vdsm	Assignee:	Dan Kenigsberg <danken>
Status:	CLOSED NEXTRELEASE	QA Contact:	Meni Yakove <myakove>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.3	CC:	acathrow, bazulay, gklein, iheim, mgoldboi, treydock, yeylon
Target Milestone:	---
Target Release:	3.3.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:	ovirt-3.3.4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-26 11:42:43 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 Trey Dockendorf 2014-02-10 17:56:57 UTC

Description of problem:

VDSM throws an error when it encounters a network interface, such as InfiniBand, that does not have an accessible "speed" file in sysfs.

Version-Release number of selected component (if applicable):

vdsm-4.13.3-3.el6

How reproducible:

Always

Steps to Reproduce:
1. Enable an infiniband interface
2. Start vdsm
3. View /var/log/messages

Actual results:

vdsm root ERROR cannot read ib0 speed#012Traceback (most recent call last):#012  File "/usr/lib64/python2.6/site-packages/vdsm/netinfo.py", line 297, in speed#012    s = int(speedFile.read())#012IOError: [Errno 22] Invalid argument

Expected results:

No message in /var/log/messages and VDSM logs "cannot read ib0 nic speed".


Additional info:

Verified that http://gerrit.ovirt.org/24197 solves this issue.