Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1053727

Summary:	[RFE][neutron]: Operational Status for Floating IPs
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-neutron	Assignee:	Assaf Muller <amuller>
Status:	CLOSED ERRATA	QA Contact:	Roey Dekel <rdekel>
Severity:	high	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	amuller, chrisw, lpeer, markmc, mlopes, nyechiel, oblaut, yeylon
Target Milestone:	Upstream M3	Keywords:	FutureFeature, Triaged
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/neutron/+spec/fip-op-status
Whiteboard:	upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_approved
Fixed In Version:	5.0-Beta/2014-05-15.2	Doc Type:	Enhancement
Doc Text:	With this update, floating IP addresses now have an operational status: 'Active', 'Down', or 'Error'. The operational status can be viewed with Dashboard and the command-line interface.	Story Points:	---
Clone Of:
Clones:	1082451 (view as bug list)		Environment:
Last Closed:	2014-07-08 15:33:47 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1003878, 1082451

Description RHOS Integration 2014-01-15 17:02:49 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/fip-op-status.

Description:

Currently floating IPs do not have an operational status.
The API returns the floating IP info, but there is no way to check whether the floating IP has actually been created or not.

The goal of this blueprint is to add an operational status concept for floating IPs.
This will add a readonly attribute to the API; it is worth doing this as a change to the core API rather than an extension.

The implementation of this blueprint will contain at least support for the ml2 plugin and a solution for ensuring other plugins are not broken by the change  and do not report meaningless statuses if they do not support it.

This will also be beneficial for tempest tests which validate network connectivity as it will allow for a better issue diagnosis.

Specification URL (additional information):

None

Comment 3 Assaf Muller 2014-03-19 13:16:11 UTC

[347393] Operational Status for Floating IPs - GUI:
Note that Horizon does not support floating IP statuses as of today.

Breakdown - 3:
Changing the VM port status does not affect floating IP status.

There is no test that expects a floating IP to end up in an error state. A floating IP can enter an error state by failing to configure NAT rules, or adding the floating IP address on the router's exterior device. For manual testing, you could perhaps change something on the system that should cause such an error, then assert that the floating-ip status is ERROR.

[347378] Operational Status for Floating IPs - Neutron:
CLI does support floating IP status.

Same remarks as the GUI test case - No error test, changing VM port status does not affect floating IP status.

Comment 4 Ofer Blaut 2014-03-23 10:05:10 UTC

The GUI does support floating ip status , so it should work in IceHouse as well

Comment 5 Ofer Blaut 2014-05-25 11:47:20 UTC

The RFE is blocked by bug - https://bugs.launchpad.net/neutron/+bug/1322990

Floating ip status is not updated both CLI and GUI 

Tested with ML+VLAN and VXLAN 

openstack-neutron-openvswitch-2014.1-20.el7ost.noarch
python-neutronclient-2.3.4-1.el7ost.noarch
python-neutron-2014.1-20.el7ost.noarch
openstack-neutron-ml2-2014.1-20.el7ost.noarch
openstack-neutron-2014.1-20.el7ost.noarch

Comment 6 Ofer Blaut 2014-05-26 04:10:32 UTC

RFE Failed QE

Comment 10 Ofer Blaut 2014-05-27 11:25:15 UTC

Tested - 
python-neutronclient-2.3.4-1.el7ost.noarch
openstack-neutron-2014.1-20.el7ost.noarch
openstack-neutron-openvswitch-2014.1-20.el7ost.noarch
python-neutron-2014.1-20.el7ost.noarch
openstack-neutron-ml2-2014.1-20.el7ost.noarch

Comment 12 errata-xmlrpc 2014-07-08 15:33:47 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0848.html