Bug 1075065

Summary:	engine should report the interface name for which "Used Network resources of host xxxxxxxx [100%] exceeded defined threshold [95%]" message is applicable.
Product:	[Retired] oVirt	Reporter:	Alona Kaplan <alkaplan>
Component:	ovirt-engine-webadmin	Assignee:	Alona Kaplan <alkaplan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Meni Yakove <myakove>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.4	CC:	acathrow, ecohen, gklein, iheim, masayag, mgoldboi, nyechiel, Rhev-m-bugs, ukar, yeylon
Target Milestone:	---
Target Release:	3.4.1
Hardware:	x86_64
OS:	Linux
Whiteboard:	network
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1070667	Environment:
Last Closed:	2014-05-08 13:36:00 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:	1070667
Bug Blocks:

Description Alona Kaplan 2014-03-11 12:16:49 UTC

+++ This bug was initially created as a clone of Bug #1070667 +++

Description of problem:
When populating "Used Network resources of host xxxxxxxx [100%] exceeded defined threshold [95%]" message it should include the in interface name as well. So that system admin can take a look into the underlying nic interfaces. 

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

How reproducible:
not sure

Steps to Reproduce:
1.
2.
3.

Actual results:
ovirt-engine is not indicating the interface name which is experiencing "Used Network resources of host xxxxxxxx [100%] exceeded defined threshold [95%]".

Expected results:
It should indicate the correct name so that appropriate action can be taken.

--- Additional comment from Nir Yechiel on 2014-03-05 09:44:15 EST ---

With the current implementation a general event is reported per host when any of the host's NICs is exceeding the threshold (based TX or RX values). This should be extended to include also the individual NIC/NICs in question.

Comment 1 Sandro Bonazzola 2014-05-08 13:36:00 UTC

This is an automated message

oVirt 3.4.1 has been released:
 * should fix your issue
 * should be available at your local mirror within two days.

If problems still persist, please make note of it in this bug report.