Bug 1607963
| Summary: | [OSP14] Initial connection from neutron-server to rabbitmq takes longer time and trigger timeout and Instance creation eventually failed. | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | John Eckersberg <jeckersb> |
| Component: | python-amqp | Assignee: | John Eckersberg <jeckersb> |
| Status: | CLOSED ERRATA | QA Contact: | Roee Agiman <ragiman> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 14.0 (Rocky) | CC: | amoralej, amuller, apevec, bcafarel, bfournie, chjones, chrisw, dalvarez, jamsmith, jeckersb, knoha, lhh, lmarsh, majopela, mariel, mfuruta, nyechiel, pablo.iranzo, ragiman, srevivo |
| Target Milestone: | Upstream M3 | Keywords: | Rebase, Triaged, ZStream |
| Target Release: | 14.0 (Rocky) | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | python-amqp-2.3.2-3.el7ost | Doc Type: | Rebase: Bug Fixes and Enhancements |
| Doc Text: |
When resolving hostnames, python-amqp requests both A and AAAA records. If an A record is successfully retrieved, a request for AAAA is still sent. If the resolver is not able to resolve the AAAA record request, the entire operation must wait for the timeout on the AAAA request. This causes name resolution to take longer than necessary and may cause AMQP messaging operations to be slow or to timeout entirely. In this update, if an A record is successfully returned, python-amqp does not request the AAAA record. It simply uses the successful A record and name lookups resolve faster.
|
Story Points: | --- |
| Clone Of: | 1569430 | Environment: | |
| Last Closed: | 2019-01-11 11:50:46 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: | 1569430 | ||
| Bug Blocks: | 1607962 | ||
|
Comment 2
John Eckersberg
2018-07-24 15:49:26 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://access.redhat.com/errata/RHEA-2019:0045 |