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

Bug 1503566

Summary: [BLOCKED on OVS-2.8] VM fails to get IP on OVN subnet without gateway
Product: [oVirt] ovirt-provider-ovn Reporter: Mor <mkalfon>
Component: providerAssignee: Marcin Mirecki <mmirecki>
Status: CLOSED CURRENTRELEASE QA Contact: msheena
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0.4CC: bugs, danken, mburman, ylavi
Target Milestone: ovirt-4.2.6Keywords: Automation
Target Release: ---Flags: rule-engine: ovirt-4.2+
rule-engine: ovirt-4.3+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-03 15:08:05 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:
Bug Depends On: 1482682, 1503820, 1505398, 1598905    
Bug Blocks:    
Attachments:
Description Flags
engine vdsm and ovn logs none

Description Mor 2017-10-18 12:03:32 UTC
Created attachment 1340139 [details]
engine vdsm and ovn logs

Description of problem:
On OVN subnet without supplied gateway, VM fails to get IP.

Version-Release number of selected component (if applicable):
4.2.0-0.0.master.20171013142622.git15e767c.el7.centos
ovirt-provider-ovn-1.2-0.20171013135342.git023d6ce.el7.centos.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create OVN network and subnet without gateway.
2. Attach the OVN network to a VM.
3. Run VM and try to get IP from the OVN network.

Actual results:
VM fails to get IP.

Expected results:
VM should get IP.

Comment 1 Marcin Mirecki 2017-10-19 12:17:10 UTC
All looks ok on the provider side, the ovn db is populated properly.
The OVN docs:   
   http://openvswitch.org/support/dist-docs/ovn-nb.5.txt
it seems that this option is not mandatory (the mandatory one's being listed a paragraph higher).

I'm inquiring with the OVN team if this is indeed so, and if so, why dhcp fails to work.

Comment 2 Marcin Mirecki 2017-10-23 13:40:09 UTC
According to findings by the OVS team, the problem is resolved in OVS 2.8
Until we move over to 2.8 the default gateway will still be mandatory.

Currently we can not move to 2.8 until BZ 1503820 is fixed.

The OVS patch that changes this (if you are interested):
https://github.com/openvswitch/ovs/commit/b89d25e5694bc9bb0a1fbb2a025d18a2a231c633

Note that the docs on the ovs site already state that the default gateway is optional, as these are the docs of the master branch, and are already updated.

Comment 3 msheena 2018-08-01 13:54:04 UTC
verified on:
ovirt-engine: 4.2.5.2-0.1.el7ev
ovn:          ovirt-provider-ovn-1.2.13-1.el7ev.noarch
ovs:          openvswitch-2.9.0-55.el7fdp.x86_64