Bug 1288097 - Command `nova floating-ip-create` fails when deploying with ospd
Summary: Command `nova floating-ip-create` fails when deploying with ospd
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 7.0 (Kilo)
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ga
: 8.0 (Liberty)
Assignee: chris alfonso
QA Contact: Daniel Mellado
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-03 14:02 UTC by Daniel Mellado
Modified: 2016-02-01 02:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-27 11:47:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1370448 0 None None None Never

Description Daniel Mellado 2015-12-03 14:02:08 UTC
Description of problem:

Tempest tests requiring floating_ip pool are failing, this seems to be an identical case as the issue in LP.

A value for the defualt nova floating pool should be added in DEFAULT/default_floating_pool

How reproducible:

Command `nova floating-ip-create` fails with ERROR: FloatingIpPoolNotFound: Floating ip pool not found. (HTTP 404) (Request-ID: req-52256308-b9ac-457e-8b5c-e1df5dcc31cd)


Actual results:

ERROR: FloatingIpPoolNotFound: Floating ip pool not found.

Expected results:

For the FIP to be created

Additional info:

https://review.openstack.org/#/c/156189/

Workaround

Run floating-ip-create command with floating IP pool specified, for instance:

nova floating-ip-create novapool

Comment 2 Alexander Chuzhoy 2015-12-07 17:09:06 UTC
Running "nova floating-ip-create  [<floating-ip-pool>]" manually works for me on 8.0.

Comment 3 Jaromir Coufal 2015-12-07 18:34:09 UTC
Dan, we could not reproduce this in 8.0, could you please verify whether you are still hitting the bug with the latest puddle?

Comment 7 Jaromir Coufal 2016-01-27 11:47:06 UTC
Thanks. Closing please re-open if the issue reappears.


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