Bug 1415829
| Summary: | Backport: [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: | 10.0 (Newton) | CC: | amuller, aperotti, apevec, dcadzow, jschluet, lhh, lpeer, mgandolf, mlopes, nlevinki, nyechiel, oblaut, pablo.iranzo, paldeala, sclewis, tfreger |
| Target Milestone: | z2 | Keywords: | FeatureBackport, FutureFeature, OtherQA, Triaged, ZStream |
| Target Release: | 10.0 (Newton) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-neutron-lbaas-9.1.0-3.el7ost | Doc Type: | Enhancement |
| Doc Text: |
This enhancement adds the ability to automatically reschedule load balancers from dead LBaaS agents. Previously, load balancers could be scheduled 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 are automatically rescheduled to a different agent.
This feature is turned off by default and controlled using `allow_automatic_lbaas_agent_failover`.
|
Story Points: | --- |
| Clone Of: | 1325861 | Environment: | |
| Last Closed: | 2017-02-23 16:34:47 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: | 1325861 | ||
| Bug Blocks: | 1046780, 1273812 | ||
|
Comment 3
Nir Magnezi
2017-02-15 13:42:33 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. https://rhn.redhat.com/errata/RHBA-2017-0314.html |