Bug 1342784

Summary:	[RFE] - [Network Filter] - Let admin define filter parameters/elements like 'DHCPSERVER' per vNIC profile
Product:	[oVirt] ovirt-engine	Reporter:	Michael Burman <mburman>
Component:	RFEs	Assignee:	Scott Herold <sherold>
Status:	CLOSED DUPLICATE	QA Contact:	Gil Klein <gklein>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.0.0	CC:	bugs, danken, ylavi
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	ylavi: ovirt-future? mburman: planning_ack? mburman: devel_ack? mburman: 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:	2016-12-25 10:17:18 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 2016-06-05 08:55:30 UTC

Description of problem:
[RFE] - [Network Filter] - Let admin define filter parameters/elements like 'DHCPSERVER' per vNIC profile. 

Currently the network filter 'allow-dhcp-server' is missing the variables/elements 'DHCPSERVER' and can't be used. 
This RFE should allow the admin/user to define such parameter by it's own in the vNIC profile dialog. 

Version-Release number of selected component (if applicable):
4.0.0-0.7.master.el7ev


Steps to Reproduce:
1. Try to run VM with 'allow-dhcp'server' network filter in the vNIC profile.

Actual results:
VM failed to run with error:

"VM vm-5 is down with error. Exit message: internal error: Cannot instantiate filter due to unresolvable variables or unavailable list elements: DHCPSERVER"

Additional info:
See also - BZ 1342782

Comment 1 Yaniv Lavi 2016-11-23 10:49:31 UTC

Didn't we add this in 4.1?

Comment 2 Dan Kenigsberg 2016-11-23 11:18:47 UTC

(In reply to Yaniv Dary from comment #1)
> Didn't we add this in 4.1?

No, only on Vdsm side.

Comment 3 Dan Kenigsberg 2016-12-25 10:17:18 UTC


*** This bug has been marked as a duplicate of bug 1366905 ***