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
[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.
The GUI does support floating ip status , so it should work in IceHouse as well
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
RFE Failed QE
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
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