Bug 1284739
| Summary: | Floating IP status is None in Multicontroller L3 router HA | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Timothy Swanson <tiswanso> | |
| Component: | openstack-neutron | Assignee: | Assaf Muller <amuller> | |
| Status: | CLOSED ERRATA | QA Contact: | Alexander Stafeyev <astafeye> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 8.0 (Liberty) | CC: | amuller, chrisw, ihrachys, itbrown, jschluet, mlopes, nauvray, nyechiel, sgaddam, slinaber, tfreger, yeylon | |
| Target Milestone: | ga | Keywords: | AutomationBlocker | |
| Target Release: | 8.0 (Liberty) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-neutron-7.0.1-9.el7ost | Doc Type: | Bug Fix | |
| Doc Text: |
Prior to this update, the status of a floating IP address was not set when the floating IP address was realized by an HA router. Consequently, 'neutron floatingip-show <floating_ip>' would not output an updated status.
With this update, a floating IP address status is updated when realized by HA routers, and when the L3 agent configures a router.
As a result, the status field for floating IP addresses realized by HA routers are now updated to 'ACTIVE' when the floating IP is configured by the L3 agent.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1305081 (view as bug list) | Environment: | ||
| Last Closed: | 2016-04-07 21:13:45 UTC | Type: | Bug | |
| 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: | 1190166, 1243520, 1305081 | |||
|
Description
Timothy Swanson
2015-11-24 04:06:49 UTC
This potential fix (not upstream yet) works for our testing:
diff --git a/neutron/agent/l3/ha_router.py b/neutron/agent/l3/ha_router.py
index 4b88a3e..25e70c7 100644
--- a/neutron/agent/l3/ha_router.py
+++ b/neutron/agent/l3/ha_router.py
@@ -247,7 +247,7 @@ class HaRouter(router.RouterInfo):
ip_cidr = common_utils.ip_to_cidr(fip_ip)
self._add_vip(ip_cidr, interface_name)
# TODO(Carl) Should this return status?
- # return l3_constants.FLOATINGIP_STATUS_ACTIVE
+ return n_consts.FLOATINGIP_STATUS_ACTIVE
def remove_floating_ip(self, device, ip_cidr):
self._remove_vip(ip_cidr)
*** Bug 1295202 has been marked as a duplicate of this bug. *** Automation blocker, setting to urgent/urgent. *** Bug 1299592 has been marked as a duplicate of this bug. *** *** Bug 1303664 has been marked as a duplicate of this bug. *** Liberty openstack-neutron-7.0.1-9.el7ost [stack@instack ~]$ neutron floatingip-list +--------------------------------------+------------------+---------------------+--------------------------------------+ | id | fixed_ip_address | floating_ip_address | port_id | +--------------------------------------+------------------+---------------------+--------------------------------------+ | 1353280b-983c-40d4-abb8-7d1164059e3c | 192.168.1.5 | 192.0.2.151 | c9374c64-42b3-42c5-8fe6-d6227e7341bf | +--------------------------------------+------------------+---------------------+--------------------------------------+ [stack@instack ~]$ neutron floatingip-show 1353280b-983c-40d4-abb8-7d1164059e3c +---------------------+--------------------------------------+ | Field | Value | +---------------------+--------------------------------------+ | fixed_ip_address | 192.168.1.5 | | floating_ip_address | 192.0.2.151 | | floating_network_id | 549e2775-8883-4882-97ce-299f53318a9c | | id | 1353280b-983c-40d4-abb8-7d1164059e3c | | port_id | c9374c64-42b3-42c5-8fe6-d6227e7341bf | | router_id | bb7117c8-53ee-433b-9da5-a8ac9c711289 | | status | ACTIVE | | tenant_id | 4bad34f9e5a144afa52b6520f7359de9 | +---------------------+--------------------------------------+ 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. https://rhn.redhat.com/errata/RHEA-2016-0603.html |