Red Hat Bugzilla – Bug 1295202
Floating IP status is blank after associating it with an instance
Last modified: 2016-04-26 12:04:25 EDT
Description of problem:
After creating a Floating IP and associating it with an instance the status of the FIP is blank with cause tempest to fail on several tests.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a floating IP
2. Associate the instance with the floating IP
# nova floating-ip-associate <instance> <FIP>
3. Verify the status of the FIP
# neutron floatingip-show
Using packstack with the following packages - no problem:
A few clarification following a chat with Itzik on irc:
*Floating IPs are working as expected. The issue is with the 'status' output which shows blank instead of 'ACTIVE'.
*This seems to be specific to OSP director based deployments.
The issue occurred using OSPD7
(In reply to Itzik Brown from comment #0)
> Steps to Reproduce:
> 1. Create a floating IP
> 2. Associate the instance with the floating IP
> # nova floating-ip-associate <instance> <FIP>
> 3. Verify the status of the FIP
> # neutron floatingip-show
did you intentionally use both nova and neutron floating ip support?
(In reply to Jon Schlueter from comment #6)
> (In reply to Itzik Brown from comment #0)
> > Steps to Reproduce:
> > 1. Create a floating IP
> > 2. Associate the instance with the floating IP
> > # nova floating-ip-associate <instance> <FIP>
> > 3. Verify the status of the FIP
> > # neutron floatingip-show
> did you intentionally use both nova and neutron floating ip support?
There are two way to associate a floating IP - to a port using Neutron or to an instance using Nova. It's convenient to use Nova.
*** Bug 1296169 has been marked as a duplicate of this bug. ***
The problem is that with HA routers we don't get the floating IP status. This is why Arie couldn't reproduce this on Packstack based jobs (No HA). It's always been like this, ever since we introduced HA routers in Juno, because I commented out this bit of code back then:
Setting as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1284739.
*** This bug has been marked as a duplicate of bug 1284739 ***