Trying to connect to Rabbit servers can timeout if only /etc/hosts entries are used

Bug #1780992 reported by Daniel Alvarez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.messaging
Fix Released
Undecided
Daniel Alvarez

Bug Description

When connecting to Rabbit endpoints through hostnames in /etc/hosts, py-amqp will try to go through the nameservers if only the IPv4 entry is present.

In those cases where compute nodes don't have any nameservers configured or those are unreachable for some reason, the initial connection to rabbit may take 60 seconds.

This patch [0] fixes it and it's present in py-amqp>=2.3.0.

[0] https://github.com/celery/py-amqp/commit/1ad97fb14c0c3c57395ca525932f95a830e51a88

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to oslo.messaging (master)

Fix proposed to branch: master
Review: https://review.openstack.org/581744

Changed in oslo.messaging:
assignee: nobody → Daniel Alvarez (dalvarezs)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to oslo.messaging (master)

Reviewed: https://review.openstack.org/581744
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=7dc76843114b21d280c27bab9d7776d7f37e3569
Submitter: Zuul
Branch: master

commit 7dc76843114b21d280c27bab9d7776d7f37e3569
Author: Daniel Alvarez <email address hidden>
Date: Wed Jul 11 15:21:56 2018 +0200

    Bump py-amqp to >= 2.3.0

    Due to the bug below we want to have py-amqp>=2.3.0 so that connecting
    to rabbit endpoints don't timeout when relying on /etc/hosts entries.
    Closes-Bug: 1780992

    Change-Id: Ia2c1114cb0f8d480695197714f7c6293751430dd

Changed in oslo.messaging:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/oslo.messaging 8.1.0

This issue was fixed in the openstack/oslo.messaging 8.1.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/requirements queens-eol

This issue was fixed in the openstack/requirements queens-eol release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.