Bug 1848474

Summary:	[OSP16.1][Routed-provider-networks]Floating ip isn't supported
Product:	Red Hat OpenStack	Reporter:	Candido Campos <ccamposr>
Component:	openstack-neutron	Assignee:	Bernard Cafarelli <bcafarel>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Eran Kuris <ekuris>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	16.1 (Train)	CC:	chrisw, ealcaniz, gurpsing, mtomaska, scohen
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
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:	2023-09-07 17:49:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1671811

Description Candido Campos 2020-06-18 12:37:57 UTC

Description of problem:
Fip can not be created over a routed provider network. Maybe it should be a RFE.

Version-Release number of selected component (if applicable):

How reproducible:

 ++ openstack floating ip create public
  Error while executing command: BadRequestException: 400, Unable to
find any IP address on external network

Comment 2 Bernard Cafarelli 2020-06-19 13:34:00 UTC

Marking this as RFE indeed, I added a relevant upstream one.

FIP on routed provider networks is not supported in OSP at the moment and needs extra parts (probably BGP speaker outside of the cloud to route to proper segment).

In envisioned uses and current reference architectures, this is not too important too as this kind of deployment will rather directly use public IPs on the routed network, and keep self-service network internal (if any)

One other use is to allow more tempest tests to run in CI in these deployments (as some rely on connecting to VMs via FIP )