Bug 1305081
| Summary: | Floating IP status is None in Multicontroller L3 router HA | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Ihar Hrachyshka <ihrachys> |
| Component: | openstack-neutron | Assignee: | Assaf Muller <amuller> |
| Status: | CLOSED ERRATA | QA Contact: | Eran Kuris <ekuris> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.0 (Kilo) | CC: | amuller, chrisw, ihrachys, itbrown, jschluet, mlopes, nauvray, nyechiel, oblaut, sclewis, sgaddam, slinaber, tfreger, tiswanso, yeylon |
| Target Milestone: | z4 | Keywords: | AutomationBlocker, Triaged, ZStream |
| Target Release: | 7.0 (Kilo) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-neutron-2015.1.2-9.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Prior to this update, the status of a floating IP was not set when the floating IP was realized by an HA router. As a result, `neutron floatingip-show <floating_ip>` might not have shown the updated status.
This update addresses this issue by updating floating IP statuses when realized by HA routers, and when the L3 agent configures a router. As a result, the status field for any floating IPs realized by HA routers is now updated to `ACTIVE` when the floating IP is configured by the L3 agent.
|
Story Points: | --- |
| Clone Of: | 1284739 | Environment: | |
| Last Closed: | 2016-02-18 16:08:29 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: | 1284739 | ||
| Bug Blocks: | 1190166, 1243520 | ||
|
Comment 1
Ihar Hrachyshka
2016-02-06 11:56:31 UTC
> I don't see flags automatically set, so I add rhos-flags@.
iirc bz needs Triaged in Keywords for auto-flaging to work
Verifies and fixed : [stack@undercloud ~]$ rpm -qa |grep neutron openstack-neutron-ml2-2015.1.2-9.el7ost.noarch openstack-neutron-common-2015.1.2-9.el7ost.noarch python-neutronclient-2.4.0-2.el7ost.noarch openstack-neutron-2015.1.2-9.el7ost.noarch openstack-neutron-openvswitch-2015.1.2-9.el7ost.noarch python-neutron-2015.1.2-9.el7ost.noarch [stack@undercloud ~]$ neutron floatingip-list +--------------------------------------+------------------+---------------------+--------------------------------------+ | id | fixed_ip_address | floating_ip_address | port_id | +--------------------------------------+------------------+---------------------+--------------------------------------+ | d5e9a051-155b-4b1b-8475-dadeda9ee9e5 | 21.0.0.5 | 192.168.1.153 | 8a22ceb0-4647-45d3-8480-cfbd7e4442f0 | | -------------------------------------+------------------+--------------------- [stack@undercloud ~]$ neutron floatingip-show d5e9a051-155b-4b1b-8475-dadeda9ee9e5 +---------------------+--------------------------------------+ | Field | Value | +---------------------+--------------------------------------+ | fixed_ip_address | 21.0.0.5 | | floating_ip_address | 192.168.1.153 | | floating_network_id | 512c0106-5797-4694-b7ae-a1dbfdd670af | | id | d5e9a051-155b-4b1b-8475-dadeda9ee9e5 | | port_id | 8a22ceb0-4647-45d3-8480-cfbd7e4442f0 | | router_id | eda8fca8-ec29-49fc-bdb2-a9c3af55c1a5 | | status | ACTIVE | | tenant_id | b2f216f62436402f98ac66f8353f3e02 | +---------------------+--------------------------------------+ Moving the bug to the assignee of the original bug. The doctext should be updated for both. 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/RHBA-2016-0262.html |