| Summary: | [RFE] [Neutron] [LBaaS v2] Loadbalancers should be rescheduled when a LBaaS agent goes offline | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Nir Magnezi <nmagnezi> | ||||
| Component: | openstack-neutron-lbaas | Assignee: | Nir Magnezi <nmagnezi> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Toni Freger <tfreger> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 9.0 (Mitaka) | CC: | amuller, aperotti, apevec, astafeye, jschluet, lhh, lpeer, mgandolf, mlopes, nlevinki, nyechiel, oblaut, pablo.iranzo, sclewis, slinaber | ||||
| Target Milestone: | Upstream M3 | Keywords: | FutureFeature, OtherQA, Triaged | ||||
| Target Release: | 11.0 (Ocata) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | openstack-neutron-lbaas-10.0.0-0.20170127182708.3a7bbbc.el7ost | Doc Type: | Enhancement | ||||
| Doc Text: |
This enhancement adds the ability to automatically reschedule load balancers from LBaaS agents that the server detects as dead. Previously, load balancers could be scheduled and realized across multiple LBaaS agents, however if a hypervisor died, the load balancers scheduled
to that node would cease operation. With this update, these load balancers will be automatically rescheduled to a different agent. This feature is disabled by default and managed using `allow_automatic_lbaas_agent_failover`.
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 1415829 (view as bug list) | Environment: | |||||
| Last Closed: | 2017-05-17 19:28:05 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: | |||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1046780, 1273812, 1415829, 1421546 | ||||||
| Attachments: |
|
||||||
|
Description
Nir Magnezi
2016-04-11 11:25:43 UTC
Created attachment 1250611 [details]
Verification Steps
attached step-by-step verification steps.
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://access.redhat.com/errata/RHEA-2017:1245 |