Rabbitfixture does not work with rabbitmq >= 3.3

Bug #1322868 reported by Daniel Widerin on 2014-05-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gavin Panella

Bug Description

RabbitMQ >= 3.3 provides Cluster Support.

The 'RABBITMQ_NODE_PORT' which is auto-generated by rabbitfixture using the allocate_ports method may acquire a port > 2^16-20.000 which will cause an error on startup because rabbitmq adds the value 20.000 by default to RABBITMQ_NODE_PORT to auto generate its RABBITMQ_DIST_PORT.

See: https://www.rabbitmq.com/configure.html#define-environment-variables

Related branches

Daniel Widerin (saily) wrote :

Setting the RABBITMQ_DIST_PORT fixes the startup issue. See attached patch.

Gavin Panella (allenap) on 2014-05-29
Changed in rabbitfixture:
status: New → Triaged
importance: Undecided → High
Daniel Widerin (saily) wrote :

Another idea would be to disable rabbitmq clustering in tests to avoid two ports beeing blocked.

Gavin Panella (allenap) wrote :

Daniel, I think I'll go with your patch. Thanks for that by the way, and sorry for my slow response; my bug subscription was... well, I don't know, but I didn't get any notification of this bug. I've fixed that, I hope.

Gavin Panella (allenap) wrote :

Thanks again for your bug and patch Daniel. I've uploaded 0.3.5 to PyPI which contains this fix.

Changed in rabbitfixture:
assignee: nobody → Gavin Panella (allenap)
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers