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

Bug 1593676

Summary:	[RFE] Provide static routes support for routers
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Marcin Mirecki <mmirecki>
Component:	ovirt-provider-ovn	Assignee:	Marcin Mirecki <mmirecki>
Status:	CLOSED ERRATA	QA Contact:	Roni <reliezer>
Severity:	low	Docs Contact:
Priority:	high
Version:	4.2.5	CC:	bgraveno, bugs, danken, mmirecki, myakove, ylavi
Target Milestone:	ovirt-4.2.5	Keywords:	FutureFeature, Rebase, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	This feature adds static routes support to ovirt-provider-ovn, as specified in https://developer.openstack.org/api-ref/network/v2/#routers-routers The appropriate REST request for this is as follows: { "router": { "routes": [ { "destination": "179.24.1.0/24", "nexthop": "172.24.3.99" }, ...	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-31 17:50:53 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 Marcin Mirecki 2018-06-21 11:17:50 UTC

Description of problem:

The routers should support static routes during router update as described by:
https://developer.openstack.org/api-ref/network/v2/#routers-routers

Static routes are crucial for routers to handle traffic from subnets not directly connected to a router.

Comment 5 Marcin Mirecki 2018-07-12 10:15:27 UTC

Needed a flag, could not reach you on irc.
Not needed anymore.

Comment 6 Yaniv Lavi 2018-07-16 11:17:20 UTC

What is the target milestone for this?

Comment 7 Meni Yakove 2018-07-17 14:26:15 UTC

ovirt-provider-ovn-1.2.12-1.el7ev.noarch
ovirt-engine-4.2.5.1_SNAPSHOT-71.g54dde01.0.scratch.master.el7ev.noarch

Comment 9 errata-xmlrpc 2018-07-31 17:50:53 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2018:2324