Bug 1402952

Summary: After upgrading OVS and using the experimental repo: VM with vNIC attached to subnet fails to get IP from DHCP
Product: [oVirt] ovirt-provider-ovn Reporter: Mor <mkalfon>
Component: driverAssignee: Marcin Mirecki <mmirecki>
Status: CLOSED NOTABUG QA Contact: Mor <mkalfon>
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: danken, myakove, ylavi
Target Milestone: ovirt-4.1.0-betaFlags: rule-engine: ovirt-4.1+
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: 2016-12-11 13:48:48 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:

Description Mor 2016-12-08 17:41:44 UTC
Description of problem:
On a clean oVirt environment with RHEL 7.3 servers, OVS version: 2.6.1-1 and the latest OVN provider RPM's from the experimental oVirt repository, a VM attached to OVN network with subnet fails to obtain IP address from DHCP. Using OVS version: 2.6.90-1 and older RPM versions of ovirt-provider-ovn and ovirt-provider-drivers it used to work as expected.

Version-Release number of selected component (if applicable):
Non-working OVS version: openvswitch-2.6.1-1.el7.x86_64
Working OVS version: openvswitch-2.6.90-1.fc24.x86_64
oVirt Engine version: 4.1.0-0.2.master.20161201131309.git6c02a32.el7.centos
Vdsm version: vdsm-4.18.999-1028.gitd5c00b9.el7.centos

How reproducible:
100%

Steps to Reproduce:
1. Install OVN on three machines: 
   - oVirt engine 4.1 with oVirt Provider OVN package installed.
   - Two oVirt Vdsm hosts with oVirt Provider OVN driver package installed.
2. Use vdsm-tool ovn-config {provider_ip} {host_ip} on each driver server, 
   to setup the OVN tunnel.
3. Create OVN network with subnet configuration: CIDR: 192.168.10.0/24, GW: 192.168.10.254 and DNS: 8.8.8.8
4. Add extra vNIC attached to the OVN network from the previous step.
5. Run the VM.
6. Connect to the terminal on the VM and use: dhclient <name of extra vNIC> to request IP address from the OVN DHCP.

Actual results:
VM fails to get IP.

Expected results:
VM should get IP.

Additional info:


Comment 1 Mor 2016-12-11 13:48:48 UTC
I am closing this ticket as not a bug. The system team built OVS from wrong branch (without IPAM handling code).