- From: Kevin Nuckolls <
- Subject: [chef] Re: Re: RabbitMQ cookbook bugs on Ubuntu/Debian -- pull request sent
- Date: Thu, 24 May 2012 16:07:30 -0500
At least on Ubuntu 10.04 the modern Rabbitmq package repository was being configured but apt-get update wasn't being run so it was just falling back to the very old rabbitmq-server package in the Canonical repository. For 10.04 that was actually 1.7.4 which didn't even have cluster_status among other things.
My fixes make it so it should install the newest stable package from the repository that RabbitMQ maintains. So no, it's no longer out of date. Right now it installs 2.8.2 on Ubuntu/Debian systems which is the latest release.
It is out of date for Redhat/CentOS/Scientific as you can see here. It's still installing the 2.6.1 RPM.
On Thu, May 24, 2012 at 3:51 PM, James Carr <
Last time I checked the cookbook was also sorely out of date (2.4.1). Is this still true?
On May 24, 2012 3:06 PM, "Kevin Nuckolls" <
I discovered that the opscode-cookbooks/rabbitmq cookbook wasn't properly installing RabbitMQ from the correct repository, nor was it setting the erlang key via the attributes. Theoretically, these problems should have only affected Ubuntu/Debian users.
This is just an announcement that I have fixed the problem and sent a pull request. I've only tested it on Ubuntu 10.04 though. If anyone is running on Redhat or CentOS and is willing to make sure that the changes I made haven't caused any regressions that'd be great.
Hope this helps. :)
Senior Software Engineer
Archive powered by MHonArc 2.6.16.