Bug 1090896

Summary:	[RFE][Event log for NIC status] User should be able to control the event frequency or mask/acknowledge it
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Meni Yakove <myakove>
Component:	ovirt-engine-webadmin-portal	Assignee:	lpeer <lpeer>
Status:	CLOSED WONTFIX	QA Contact:	Meni Yakove <myakove>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.5.0	CC:	ecohen, gklein, iheim, mpavlik, nyechiel, rbalakri, Rhev-m-bugs, yeylon
Target Milestone:	---	Keywords:	FutureFeature, TestOnly
Target Release:	---	Flags:	nyechiel: Triaged+
Hardware:	All
OS:	Linux
Whiteboard:	network
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-29 09:06:09 UTC	Type:	Bug
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:	1120659, 1120670
Bug Blocks:

Description Meni Yakove 2014-04-24 11:21:07 UTC

Description of problem:
There is a new feature Display of NIC Slave/Bond fault on RHEV-M Event Log and UI
https://bugzilla.redhat.com/show_bug.cgi?id=987299

The event log won't be more than one event per interface each 30 minutes so if the interface is flapping the user have no way to know.
In this case the event should count the times that the interface was in the state and in the event log display the count.

if the interface go down 5 times in 30 minutes so we will have event that the interface is down in the first down stat and another event after 30 minutes with "<Interface> enter down state 5 time in 30 minutes"




Additional info:

Comment 1 Nir Yechiel 2014-07-17 12:15:16 UTC

The solution should be more general and not specific for this specific event. I have suggested system-wide solutions on BZ 1120670 and BZ 1120659, so I am turning this into a place older for network QE to verify the NIC up/down event once we have them implemented.

Comment 2 Itamar Heim 2015-03-29 09:06:09 UTC

Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.