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

Bug 1608885

Summary: ovn localnet - Custom bridge/vlan is not passed to the guest
Product: [oVirt] ovirt-provider-ovn Reporter: Michael Burman <mburman>
Component: providerAssignee: Marcin Mirecki <mmirecki>
Status: CLOSED NOTABUG QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.2.7CC: bugs, danken, ylavi
Target Milestone: ovirt-4.2.6Flags: rule-engine: ovirt-4.2+
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: 2018-07-30 15:02:50 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:
Attachments:
Description Flags
logs none

Description Michael Burman 2018-07-26 12:46:01 UTC 
Description of problem:
ovn localnet - Custom bridge/vlan is not passed to the guest 

When setting a custom data center network for ovn local net, it is not passed to the guest. 
If the data center has custom bridge name and segmentation id, the custom values not passed to the guest. 

Version-Release number of selected component (if applicable):
ovirt-provider-ovn-1.2.13-1.el7ev.noarch
4.2.6_SNAPSHOT-84.gad3de30.0.scratch.master.el7ev

How reproducible:
100%

Steps to Reproduce:
1. Add host to OVS cluster
2. Create a native vlan network with more than 15 characters
3. Attach the network to the host
4. Take it's vdsm name, for example on7ac5f1d5d5d94
5. Create new ovn network on the provider via the engine UI and choose a custom data center network, set the vdsm name in
6. Attach profile to VMs vNIC with the ovn network
7. Start VM 

Actual results:
The custom values not passed to the guest, VM didn't get IP from the vlan

Expected results:
custom values should pass to the VM
Comment 1 Michael Burman 2018-07-26 13:02:22 UTC 
I see the custom bridge is passed to provider, but for some reason it doesn't work if i use the custom values. 
2018-07-26 15:58:26,411 root Response body: {"network": {"status": "ACTIVE", "name": "test2", "provider:physical_network": "onabcc37480d2e4", "tenant_id": "00000000000000000000000000000001", "provider:network_type": "flat", "id": "c3e0be2c-1339-4902-8480-143fb3dfc234", "mtu": 1442}}


If i use the same network, but choose it a name network from the drop down list, it works fine.
Comment 2 Michael Burman 2018-07-26 13:03:43 UTC 
Created attachment 1470771 [details]
logs
Comment 3 Marcin Mirecki 2018-07-30 15:02:50 UTC 
In step 5 (5. Create new ovn network on the provider via the engine UI and choose a custom data center network, set the vdsm name in) you need to additionally populate the vlan id field.
Comment 4 Michael Burman 2018-07-31 08:27:48 UTC 
(In reply to Marcin Mirecki from comment #3)
> In step 5 (5. Create new ovn network on the provider via the engine UI and
> choose a custom data center network, set the vdsm name in) you need to
> additionally populate the vlan id field.

I don't like it, but ok. The vlan id should have been populated from the custom bridge.
Comment 5 Marcin Mirecki 2018-07-31 09:07:10 UTC 
It is populated when you don't use custom.
Custom means you have to do everything yourself, including setting vlan id, which allows you using networks not managed by engine.
Comment 6 Michael Burman 2018-07-31 11:22:28 UTC 
(In reply to Marcin Mirecki from comment #5)
> It is populated when you don't use custom.
> Custom means you have to do everything yourself, including setting vlan id,
> which allows you using networks not managed by engine.

ACK
Although this custom network does managed by the engine, you just use it's vdsm name instead of the native network name