Bug 1365378
| Summary: | openvswitch agents are being reported as down for 10 minutes after all reset controllers come back online | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | John Schwarz <jschwarz> |
| Component: | openstack-neutron | Assignee: | John Schwarz <jschwarz> |
| Status: | CLOSED ERRATA | QA Contact: | Toni Freger <tfreger> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 8.0 (Liberty) | CC: | adahms, amuller, chrisw, jjoyce, michele, mkrcmari, nyechiel, oblaut, sclewis, srevivo, tfreger |
| Target Milestone: | async | Keywords: | ZStream |
| Target Release: | 8.0 (Liberty) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-neutron-7.1.1-5.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Previously, if all controller nodes restarted at the same time, it would cause all amqp (rabbitmq) servers to also restart. This caused the connection between Neutron agents and the amqp servers to appear to hang until timed-out, while the time-out length is linear (60 seconds, then 120, then 240... limited at 600), preventing agents from receiving any events until the timeout expires. With this update, the timeout mechanism in the specific event that tries to connect between the agents and the neutron-server was changed to always be 60 seconds. Now, if the connection hangs because of a restart of all controller nodes, the agents recover quicker (up to 60 seconds after the controllers fully start again).
|
Story Points: | --- |
| Clone Of: | 1359894 | Environment: | |
| Last Closed: | 2016-09-14 14:42:41 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: | 1359894 | ||
| Bug Blocks: | |||
|
Comment 2
Toni Freger
2016-09-07 18:12:01 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-2016-1872.html |