Bug 1296169 - Floating IP status is blank after associating it with an instance
Summary: Floating IP status is blank after associating it with an instance
Keywords:
Status: CLOSED DUPLICATE of bug 1295202
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 8.0 (Liberty)
Assignee: lpeer
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-06 14:00 UTC by Itzik Brown
Modified: 2016-04-26 14:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-13 15:45:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Itzik Brown 2016-01-06 14:00:53 UTC 
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):
OSPD8 
RHEL7.2
python-neutron-7.0.1-2.el7ost.noarch
openstack-neutron-7.0.1-2.el7ost.noarch
openstack-neutron-openvswitch-7.0.1-2.el7ost.noarch


How reproducible:


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

Actual results:


Expected results:


Additional info:
Comment 2 Assaf Muller 2016-01-13 15:45:19 UTC 

*** This bug has been marked as a duplicate of bug 1295202 ***
Note You need to log in before you can comment on or make changes to this bug.