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

Bug 915778

Summary: [RFE][RHEVM] [webadmin] Network Interfaces statistics are not shown for VM unless VNIC is selected
Product: Red Hat Enterprise Virtualization Manager Reporter: Martin Pavlik <mpavlik>
Component: ovirt-engine-webadmin-portalAssignee: Alona Kaplan <alkaplan>
Status: CLOSED ERRATA QA Contact: Martin Pavlik <mpavlik>
Severity: unspecified Docs Contact:
Priority: low    
Version: 3.2.0CC: acathrow, alkaplan, danken, ecohen, gklein, iheim, jkt, masayag, myakove, Rhev-m-bugs
Target Milestone: ---Keywords: FutureFeature, Improvement, Triaged
Target Release: 3.3.0Flags: sgrinber: Triaged+
Hardware: x86_64   
OS: Linux   
Whiteboard: network
Fixed In Version: is1 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-21 17:14:24 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:
Attachments:
Description Flags
screenshot 1 none

Description Martin Pavlik 2013-02-26 13:44:13 UTC
Created attachment 702871 [details]
screenshot 1

Description of problem:
Network Interfaces statistics are not show for VM unless some VNIC is selected (see screenshot)

Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Manager Version: 3.2.0-9.el6ev 

How reproducible:
100%

Steps to Reproduce:
1. create VM with at least one VNIC
2. Virtual Machines -> your VM -> Network Interfaces
  
Actual results:
Statistics field is empty until some VNIC is slected

Expected results:
Statistics should be displayed on Virtual Machines -> your VM -> Network Interfaces (no need to select some VNIC)

Additional info:

Comment 1 Dan Kenigsberg 2013-02-28 10:50:25 UTC
Yeah, it would be nice if when the subtab is opened, the most-active VNIC would be auto-selected, so that its statistics is shown.

However, I do not think it warrants a beta exception.

Comment 2 Alona Kaplan 2013-03-11 09:16:29 UTC
(In reply to comment #1)
> Yeah, it would be nice if when the subtab is opened, the most-active VNIC
> would be auto-selected, so that its statistics is shown.
Danken- what do you mean by "most-active"?
I suggest-
When the subtab is opened, the first VNIC in the table will be auto-selected.

Comment 3 Dan Kenigsberg 2013-03-11 09:46:43 UTC
(In reply to comment #2)

> Danken- what do you mean by "most-active"?
> I suggest-
> When the subtab is opened, the first VNIC in the table will be auto-selected.

I can live with this. in 95% of the cases it the only - and thus most active - vnic.

Comment 4 Alona Kaplan 2013-03-20 15:19:05 UTC
So what should I do with this bug?

Comment 6 Meni Yakove 2013-05-26 07:46:34 UTC
Verified on rhevm-3.3.0-0.3.master.el6ev.noarch

Comment 7 Charlie 2013-11-28 00:12:27 UTC
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Comment 9 errata-xmlrpc 2014-01-21 17:14:24 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.

http://rhn.redhat.com/errata/RHSA-2014-0038.html