[Bug 232246] devel/py-oslo.messaging: Fix for the RabbitMQ driver when used with Python 3+

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232246

            Bug ID: 232246
           Summary: devel/py-oslo.messaging: Fix for the RabbitMQ driver
                    when used with Python 3+
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: sunpoet at FreeBSD.org
          Reporter: freebsd_ports at k-worx.org
                CC: python at FreeBSD.org, sunpoet at FreeBSD.org
             Flags: maintainer-feedback?(sunpoet at FreeBSD.org)
          Assignee: sunpoet at FreeBSD.org
 Attachment #198134 maintainer-approval?(sunpoet at FreeBSD.org)
             Flags:
                CC: sunpoet at FreeBSD.org

Created attachment 198134
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=198134&action=edit
py-oslo.messaging-fix-rabbitmq-py36.patch

Hello,

attached is the patch that fixes the RabbitMQ driver (=
oslo_messaging/_drivers/impl_rabbit.py) on FreeBSD when used as Python 3+
package.

Without the patch the RabbitMQ messaging driver tries to use a timeout for a
newly created TCP socket but will fail shortly afterwards because FreeBSD
doesn't implement the TCP_USER_TIMEOUT option (RFC 5482) (yet?).

This leads into spawning multiple embryonic TCP connections that are never
going into the ESTABLISHED state. 

The issue has been discovered during runtime-tests of the misc/py-cinder port
in conjunction with a RabbitMQ messaging server. Please see also the attached
logfile for further details.

QA:
~~~
- poudriere (10.4-, 11.2-RELEASE, 12.0-ALPHA9 amd64 + i386) for each py27 +
py36 flavor -> OK
- portlint -> OK

-- 
You are receiving this mail because:
You are on the CC list for the bug.