Ask Your Question
0

No floating IP addresses available [closed]

asked 2016-05-10 09:21:34 -0500

glowe1 gravatar image

Hi All,

I'm using the Mitaka OpenStack on an all-in-one setup. When I try to associate a floating IP, it doesn't find one. I know there should be some available, as this shows me there are only 2 in use:

[root@openstack test-grant(keystone_admin)]# neutron floatingip-list +--------------------------------------+------------------+---------------------+--------------------------------------+ | id | fixed_ip_address | floating_ip_address | port_id | +--------------------------------------+------------------+---------------------+--------------------------------------+ | 39d24eef-9743-4c70-870f-2cc43936e848 | 192.168.0.4 | 10.3.8.163 | ccf8d872-c518-47db-93f8-ead841f6d9c9 | | 66b2e3e9-20cc-4cea-81ae-184554b5bc15 | 192.168.0.3 | 10.3.8.162 | 7c640741-0111-495c-9945-aee88649fc6c | +--------------------------------------+------------------+---------------------+--------------------------------------+ [root@openstack test-grant(keystone_admin)]#

When I created the floating IP range, I assigned 10.3.8.161-168. So why aren't the other IPs showing up? I had created some other instances that had floating IPs, but have since deleted them, so I thought OpenStack would release them.

Please advise. Thanks.

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by glowe1
close date 2016-05-16 10:51:31.419677

1 answer

Sort by ยป oldest newest most voted
1

answered 2016-05-10 10:31:54 -0500

dbaxps gravatar image

FIPs allocated to deleted instances , you may find here

image description

Then create new VM , navigate to Access& Security=>Floating IPs and reassign previously allocated FIP to your project to newly created VM.

edit flag offensive delete link more

Comments

This is what I was looking for. Thanks.

glowe1 gravatar imageglowe1 ( 2016-05-11 10:13:46 -0500 )edit

Looks like I'm still having problems. I dissociated the FIP, created a new instance. and now I can't assign any more FIPs. This is odd as I have several unnassigned FIPs in my allocation pool, and I made sure I disassociated the unused FIPs. Where do I go from here?

glowe1 gravatar imageglowe1 ( 2016-05-16 16:55:35 -0500 )edit

Attempt create new VM with fixed IP. Navigate to panel above. Select free FIP and click button "Associate".
You should get option NewVMname:assignedFixedIP link free FIP from the pool, if your previous setup of Openstack is correct. It works for me on multinode RDO Mitaka deployments.

dbaxps gravatar imagedbaxps ( 2016-05-16 17:04:49 -0500 )edit

Panel above also allows to allocate new FIPs for project from available pool. I suggest reopen question if problem still persists.

dbaxps gravatar imagedbaxps ( 2016-05-16 17:07:25 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2016-05-10 09:21:34 -0500

Seen: 357 times

Last updated: May 10 '16