Bug 1090896 - [RFE][Event log for NIC status] User should be able to control the event frequency or mask/acknowledge it
Summary: [RFE][Event log for NIC status] User should be able to control the event freq...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.5.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: lpeer
QA Contact: Meni Yakove
URL:
Whiteboard: network
Depends On: 1120659 1120670
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-24 11:21 UTC by Meni Yakove
Modified: 2016-02-10 19:49 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-29 09:06:09 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:
nyechiel: Triaged+


Attachments (Terms of Use)

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.


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