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

Bug 1536791

Summary: Provider should support using fixed_ips with PORT entities
Product: [oVirt] ovirt-provider-ovn Reporter: Mor <mkalfon>
Component: providerAssignee: Marcin Mirecki <mmirecki>
Status: CLOSED CURRENTRELEASE QA Contact: Mor <mkalfon>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: bugs, danken, lveyde, mmirecki, ylavi
Target Milestone: ovirt-4.2.2Keywords: Automation
Target Release: ---Flags: rule-engine: ovirt-4.2+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-provider-ovn-1.2.7-2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 11:16:10 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 Mor 2018-01-21 09:39:07 UTC 
Description of problem:
ovirt-provider-ovn should support using 'fixed_ips' property with port entities.

Possible -by port- work flows:
- When adding a router interface by port on a network that has a subnet, there should be a way to get the IP that is assigned to the port, and use it to configure a static route on guests.

- When adding a router interface by port on a network with multiple subnets, there should be a way to set the IP address for a specific subnet in the network.

- When adding a router interface by port on a network with multiple subnets, customer can specify a subnet id to get IP from.

- (Less common) when adding a router by port on a network with subnet, there should be a way to set the IP that is assigned to the port, in case a customer wish to specify a specific address (fixed IP) from the IP range.

Version-Release number of selected component (if applicable):
RHV 4.2.1.1-0.1.el7

Additional info:
https://developer.openstack.org/api-ref/network/v2/#ports
Comment 1 Yaniv Lavi 2018-02-07 09:03:57 UTC 
*** Bug 1530053 has been marked as a duplicate of this bug. ***
Comment 2 Mor 2018-02-25 11:31:41 UTC 
Patch: http://gerrit.ovirt.org/87421 is not merged, why this is ON_QA?
Comment 3 Marcin Mirecki 2018-02-27 08:24:54 UTC 
Removed patch: https://gerrit.ovirt.org/#/c/87421/
It is
Comment 4 Mor 2018-02-27 15:02:30 UTC 
Verified on:
ovirt-provider-ovn-1.2.7-2.el7ev.noarch
RHV 4.2.2.1-0.1
Comment 5 Sandro Bonazzola 2018-03-29 11:16:10 UTC 
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 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.