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

Bug 1482030

Summary: While updating the network vNIC profile to be with clean traffic ,and running the VM, IP parameter doesn't configure on the bridge
Product: [oVirt] ovirt-engine Reporter: Ori Ben Sasson <obensass>
Component: BLL.NetworkAssignee: Dan Kenigsberg <danken>
Status: CLOSED DUPLICATE QA Contact: Meni Yakove <myakove>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: bugs, michal.skrivanek, obensass
Target Milestone: ---Keywords: Automation, Regression
Target Release: ---   
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-08-17 05:02:14 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 Ori Ben Sasson 2017-08-16 10:08:52 UTC 
Description of problem:
While updating the network vNIC profile to be with clean traffic ,and running the VM, IP parameter doesn't configure on the bridge

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.0-0.0.master.20170815155420.gitaed789a.el7.centos.noarch
vdsm-4.20.2-33.gite85019b.el7.centos.x86_64


How reproducible:
100

Steps to Reproduce:
1. Update/Add network vNIC profile to be with clean-traffic
2. run VM
3. update/Add VM NIC with clean traffic filter parameters via REST 

Actual results:
IP parameter doesn't configure on the bridge

Expected results:
IP should be configured on libvirt interface

Additional info:
get xml from the vm: virsh -r dumpxml <vm_name>
<interface type='bridge'>
	<mac address='00:1a:4a:16:20:16'/>
	<source bridge='ovirtmgmt'/>
	<target dev='vnet1'/>
	<model type='virtio'/>
	<filterref filter='clean-traffic'/>
	<alias name='net1'/>
	<address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
</interface>
Comment 1 Michal Skrivanek 2017-08-17 05:00:52 UTC 
logs?
Comment 2 Michal Skrivanek 2017-08-17 05:02:14 UTC 
ah, nevermind...

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