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

Bug 1487907

Summary:	[RFE][UI] - Display network filter parameters under VM's network interfaces sub tab
Product:	[oVirt] ovirt-engine	Reporter:	Michael Burman <mburman>
Component:	BLL.Network	Assignee:	Ales Musil <amusil>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.2.0	CC:	bugs, danken
Target Milestone:	ovirt-4.2.0	Keywords:	FutureFeature
Target Release:	4.2.0	Flags:	danken: ovirt-4.2? gklein: testing_plan_complete- rule-engine: planning_ack? rule-engine: devel_ack+ myakove: testing_ack+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 11:45:17 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:

Description Michael Burman 2017-09-03 07:30:31 UTC

Description of problem:
[UI] - Display network filter parameters under VM's network interfaces sub tab.

As part of the Network Filter Parameters RFE - BZ 1366905 ,  the VM network communication can by restricted using the already available feature called network filters. The feature introduced in BZ 1366905 adds the ability to configure these filters by parameters via the UI and REST.

We should add those values to be displayed under VM's network interfaces once configured. 

Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20170901193740.git7900511.el7.centos

Comment 1 Michael Burman 2017-10-23 05:57:48 UTC

Verified on - 4.2.0-0.0.master.20171022103432.gitaf9d8b6.el7.centos

Comment 2 Sandro Bonazzola 2017-12-20 11:45:17 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.