Ask Your Question

Cannot associate floating-ip

asked 2013-05-16 04:40:44 -0500

Shrirang gravatar image


I followed following doc for Openstack folsom installation: (

Everything worked successfully till last step where you need to associate floating IP. Whenever I try to associate floating IP I get following error:

root@control:/home/control# quantum floatingip-associate 1efdde72-7438-45d0-b495-2ee3352a7f58 fff4169b-191e-4b4c-9e6d-114a557986b1

Bad floatingip request: Port fff4169b-191e-4b4c-9e6d-114a557986b1 is associated with a different tenant than Floating IP 1efdde72-7438-45d0-b495-2ee3352a7f58 and therefore cannot be bound.

I tried following steps to resolve this issue:

  1. Tried above command with "admin" "adminusername" "adminpassword"
  2. Tried above command with "projectone" "projectoneusername" "projectone_password"

Also whenever I try to start an instance I get the following error in instance logs:

===== cloud-final: system completely up in 53.89 seconds ==== wget: can't connect to remote host ( Network is unreachable wget: can't connect to remote host ( Network is unreachable wget: can't connect to remote host ( Network is unreachable

Can anyone please help me out?

edit retag flag offensive close merge delete



Please provide the output of 'quantum floatingip-show 1efdde72-7438-45d0-b495-2ee3352a7f58' and 'quantum port-show fff4169b-191e-4b4c-9e6d-114a557986b1' and 'quantum port-list'

darragh-oreilly gravatar imagedarragh-oreilly ( 2013-05-18 04:34:27 -0500 )edit

3 answers

Sort by ยป oldest newest most voted

answered 2013-05-20 16:17:07 -0500

The issue is because the tenant who allocated the floatingip address is different than the tenant who owns the port that you are trying to associate it with.

edit flag offensive delete link more

answered 2013-05-18 22:11:38 -0500

I have the same problem. Did you find any solution for this?

edit flag offensive delete link more

answered 2013-05-16 15:38:41 -0500

darow1 gravatar image

updated 2013-05-16 15:39:23 -0500

I also have this same issue, and have tried to use "floatingip-disassociate" command, however the output from "Quantum floatingip-list" continues to show an existing association.

Does anyone have an answer for this issue?

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2013-05-16 04:40:44 -0500

Seen: 1,583 times

Last updated: May 20 '13