Bug 1848474 - [OSP16.1][Routed-provider-networks]Floating ip isn't supported
Summary: [OSP16.1][Routed-provider-networks]Floating ip isn't supported
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Bernard Cafarelli
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks: 1671811
TreeView+ depends on / blocked
 
Reported: 2020-06-18 12:37 UTC by Candido Campos
Modified: 2023-09-07 17:49 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-07 17:49:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1667329 0 None None None 2020-06-19 08:29:21 UTC
Red Hat Issue Tracker OSP-2384 0 None None None 2022-03-24 13:38:29 UTC

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 )


Note You need to log in before you can comment on or make changes to this bug.