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

Bug 1532046

Summary: ovn localnet: attachment of ovn network to data center network is not saved
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: high Docs Contact:
Priority: high    
Version: 4.2.0CC: amusil, bugs, danken, lveyde
Target Milestone: ovirt-4.2.1Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.1.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-12 11:49:02 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:    
Bug Blocks: 1530675    
Attachments:
Description Flags
Logs none

Description Michael Burman 2018-01-07 16:59:20 UTC 
Description of problem:
Data center network doesn't saved after approving operation 

The new RFE Bug 1530675 - [RFE] ovn-localnet: Connect OVN network and oVirt Data Center Network extend ovirt-ovn-provider adding support for physical network access. It should allow user to connect external OVN networks to a physical (oVirt Data Center) network. 
But when choosing the data center network in the edit ovn network dialog, the network don't get saved. And maybe because of that it don't get passed to the VM. Currently this RFE doesn't work because of that.

When looking at the host(on VM run), it is seems that the change applied successfully - 

Bridge "vdsmbr_tdR71SYh"
        Port "net-2"
            tag: 162
            Interface "net-2"

But we can't get the correct IP from the vlan, we get the ovn's network IP and not the physical one.

Version-Release number of selected component (if applicable):
rhvm-4.2.1-0.2.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create ovn network and logical network in the DC. Attach the logical network to the host.
2. Edit ovn network and check the new 'Connect to physical network' check box 
3. Approve operation
4. Edit ovn network again and check if the changes were applied
5. Run VM using ovn network
6. Check ovs-vsctl show on host 

Actual results:
4 - The changes are gone
5 - VM is running, but getting the wrong IP, not from the phys net.
6 - On host, it seems to be fine

Expected results:
Should work as expected. 

Additional info:
Comment 1 Michael Burman 2018-01-07 17:00:35 UTC 
The cluster type is OVS + ovn network provider
Comment 2 Michael Burman 2018-01-07 17:05:32 UTC 
Created attachment 1378160 [details]
Logs
Comment 3 Michael Burman 2018-01-14 14:04:41 UTC 
Ales,

I'm testing this fix on 4.2.1.1-0.1.el7 and i found out that now it's not possible to edit and set ovn network with physical network after been created, only on the new network flow and i'm not sure it's ok. We should be able to set the physical network also after the ovn network already created, am i right?
Comment 4 Ales Musil 2018-01-15 07:15:57 UTC 
Hi Michael,

editing is currently not supported. However it is planned for future.
Comment 5 Michael Burman 2018-01-15 09:42:21 UTC 
(In reply to Ales Musil from comment #4)
> Hi Michael,
> 
> editing is currently not supported. However it is planned for future.

BZ 1514922 will handle the edit flow for 4.3
Comment 6 Michael Burman 2018-01-15 13:04:24 UTC 
Verified on - 4.2.1.1-0.1.el7
Comment 7 Sandro Bonazzola 2018-02-12 11:49:02 UTC 
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.