Bug 1487907 - [RFE][UI] - Display network filter parameters under VM's network interfaces sub tab
Summary: [RFE][UI] - Display network filter parameters under VM's network interfaces s...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.2.0
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ovirt-4.2.0
: 4.2.0
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-03 07:30 UTC by Michael Burman
Modified: 2019-04-28 13:08 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:45:17 UTC
oVirt Team: Network
Embargoed:
danken: ovirt-4.2?
gklein: testing_plan_complete-
rule-engine: planning_ack?
rule-engine: devel_ack+
myakove: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 81892 0 master MERGED webadmin: Add Network Filter Parameters info under VM network interface 2017-10-17 15:04:02 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.