RabbitMQ® for PCF Release Notes

Note: This version of RabbitMQ for PCF is no longer supported because it has reached the End of General Support phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

Upgrade to the Latest Version

Pivotal recommends that you upgrade to the latest version of your current minor line, then upgrade to the latest available version of the new minor line. For example, if you use an older v1.13.x version, upgrade to the latest v1.13.x version before upgrading to the latest v1.14.x version.

For product versions and upgrade paths, see the Product Compatibility Matrix.

Pivotal Is Continuing Support for the Pre-Provisioned Service

Previous deprecation warnings for the pre-provisioned service are no longer in effect. Pivotal continues to support the pre-provisioned service.

For information about migrating from the pre-provisioned service to the on-demand service, see About Migrating a Pre-Provisioned Instance to an On-Demand Instance. For instructions on how to install, configure, and deploy RabbitMQ for PCF as an on-demand service, see Installing and Configuring RabbitMQ for PCF the On-Demand Service.

v1.14.14

Release Date: June 17, 2019

Resolved Issue

This release has the following fix:

  • The pre-provisioned broker now terminates failed TCP connections when unbinding services. This prevents the file descriptor limit on the HAProxy and the pre-provisioned broker VMs from reaching capacity over time.

Known Issues

This release has the following known issues:

Packages

  • OSS RabbitMQ v3.7.14 - Release notes
  • Erlang v20.3.8.21
  • HAProxy v1.8.20

v1.14.13

Release Date: May 21, 2019

Resolved Issue

This release has the following fix:

  • The pre-provisioned broker now terminates failed TCP connections for the bind, provision, and deprovision broker endpoints. This prevents the file descriptor limit on the HAProxy and the pre-provisioned broker VMs from reaching capacity over time.

    Note: TCP connections still fail to terminate when unbinding services.

Known Issues

This release has the following known issues:

  • The pre-provisioned broker does not terminate failed TCP connections when unbinding services. Over time, this can cause the file descriptor limit on the VMs that host HAProxy and the pre-provisioned broker to reach capacity:
    • When capacity is reached on the HAProxy VM, RabbitMQ is unreachable.
    • When capacity is reached on the pre-provisioned broker, app developers cannot create, bind, unbind, or delete service instances.
    To resolve the issue, do one of the following:

Packages

  • OSS RabbitMQ v3.7.14 - Release notes
  • Erlang v20.3.8.20
  • HAProxy v1.8.19

v1.14.12

Release Date: May 17, 2019

Features

New features and changes in this release:

  • Errands and the pre-provisioned service broker can be deployed over HTTPS.
  • Updates OSS RabbitMQ to 3.7.14

Security Fix

This release includes the following security fix:

Resolved Issue

This release fixes the following issue:

  • An issue with service metrics caused zombie processes to accumulate on rabbitmq-server VMs.

Known Issues

This release has the following known issues:

  • The pre-provisioned broker does not terminate failed TCP connections when the request fails with a 4xx status code and when unbinding services. Over time, this can cause the file descriptor limit on the VMs that host HAProxy and the pre-provisioned broker to reach capacity:
    • When capacity is reached on the HAProxy VM, RabbitMQ is unreachable.
    • When capacity is reached on the pre-provisioned broker, app developers cannot create, bind, unbind, or delete service instances.
    To resolve the issue, do one of the following:
  • The pre-provisioned broker does not terminate failed TCP connections when the request fails with a 4xx status code and when unbinding services. Over time, this can cause the file descriptor limit on the VMs that host HAProxy and the pre-provisioned broker to reach capacity:
    • When capacity is reached on the HAProxy VM, RabbitMQ is unreachable.
    • When capacity is reached on the pre-provisioned broker, app developers cannot create, bind, unbind, or delete service instances.
    To resolve the issue, do one of the following:

Packages

  • OSS RabbitMQ v3.7.14
  • Erlang v20.3.8.20
  • HAProxy v1.8.19

v1.14.10

Release Date: March 28, 2019

Breaking Change: RabbitMQ for PCF v1.14 and later requires a Xenial stemcell. You must manually download and import a new stemcell into the Ops Manager Stemcell Library before deploying RabbitMQ for PCF v1.14. This might break automation you have set up to update RabbitMQ for PCF deployments that used Trusty stemcells. To download the Xenial stemcell from Pivotal Network, go to Stemcells for PCF (Ubuntu Xenial). For instructions on importing the stemcell, see Importing and Managing Stemcells.

Breaking Change: Syslog forwarding uses RFC5424 format, and the Legacy Format is no longer available. If you are upgrading and have Legacy Format selected in your existing syslog configuration, that setting is automatically reconfigured to use the RFC5424 format.

Resolved Issues

This release fixes the following issue:

  • Issues with the configuration of pre-provisioned RabbitMQ with external load balancers

Known Issues

This release has the following known issues:

  • The pre-provisioned broker does not terminate failed TCP connections when the request fails with a 4xx status code and when unbinding services. Over time, this can cause the file descriptor limit on the VMs that host HAProxy and the pre-provisioned broker to reach capacity:
    • When capacity is reached on the HAProxy VM, RabbitMQ is unreachable.
    • When capacity is reached on the pre-provisioned broker, app developers cannot create, bind, unbind, or delete service instances.
    To resolve the issue, do one of the following:

Packages

  • OSS RabbitMQ v3.7.13
  • Erlang v20.3.8.20
  • HAProxy v1.8.19

v1.14.9

Release Date: March 14, 2019

Breaking Change: RabbitMQ for PCF v1.14 and later requires a Xenial stemcell. You must manually download and import a new stemcell into the Ops Manager Stemcell Library before deploying RabbitMQ for PCF v1.14. This might break automation you have set up to update RabbitMQ for PCF deployments that used Trusty stemcells. To download the Xenial stemcell from Pivotal Network, go to Stemcells for PCF (Ubuntu Xenial). For instructions on importing the stemcell, see Importing and Managing Stemcells.

Breaking Change: Syslog forwarding uses RFC5424 format, and the Legacy Format is no longer available. If you are upgrading and have Legacy Format selected in your existing syslog configuration, that setting is automatically reconfigured to use the RFC5424 format.

Features

New features and changes in this release:

  • Adds RabbitMQ 3.7.13

Known Issues

This release has the following known issues:

  • The pre-provisioned broker does not terminate failed TCP connections when the request fails with a 4xx status code and when unbinding services. Over time, this can cause the file descriptor limit on the VMs that host HAProxy and the pre-provisioned broker to reach capacity:
    • When capacity is reached on the HAProxy VM, RabbitMQ is unreachable.
    • When capacity is reached on the pre-provisioned broker, app developers cannot create, bind, unbind, or delete service instances.
    To resolve the issue, do one of the following:
  • [Security Issue] The method for generating the Erlang cookie is not secure. For more information about this security issue, see CVE-2018-1279: RabbitMQ cluster compromise due to deterministically generated cookie.

  • An issue with service metrics causes zombie processes to accumulate on rabbitmq-server VMs. This can cause the VM to run out of resources and BOSH to restart it. If this occurs, Pivotal recommends that you stop the service-metrics job. However, if you stop the job, metrics will not be available.

  • Cluster scaling or changing the Erlang Cookie value requires cluster downtime, and might result in failed deployments. For more information, see Cluster Scaling Known Issue and Changing the Erlang Cookie Value Known Issue.

  • Changing networks or IP addresses for the RabbitMQ Server job results in a failed deployment. For more information, see Changing Network or IP Addresses Results in a Failed Deployment.

  • When errand run rules are set to When Changed, Ops Manager may not run the errands when the tile has relevant changes. For more information, see Managing Errands in Ops Manager. Pivotal recommends leaving the default run rule set to On.

  • There are issues with the configuration of pre-provisioned RabbitMQ with external load balancers.

  • Shareable instances are enabled in the Global Settings for On-Demand Plans tab for the pre-provisioned service as well as the on-demand service. For how to enable shareable instances, see Configure Global Settings.

Packages

  • OSS RabbitMQ v3.7.13
  • Erlang v20.3.8.20
  • HAProxy v1.8.19

v1.14.8

Release Date: March 11, 2019

Breaking Change: RabbitMQ for PCF v1.14 and later requires a Xenial stemcell. You must manually download and import a new stemcell into the Ops Manager Stemcell Library before deploying RabbitMQ for PCF v1.14. This might break automation you have set up to update RabbitMQ for PCF deployments that used Trusty stemcells. To download the Xenial stemcell from Pivotal Network, go to Stemcells for PCF (Ubuntu Xenial). For instructions on importing the stemcell, see Importing and Managing Stemcells.

Breaking Change: Syslog forwarding uses RFC5424 format, and the Legacy Format is no longer available. If you are upgrading and have Legacy Format selected in your existing syslog configuration, that setting is automatically reconfigured to use the RFC5424 format.

Features

New features and changes in this release:

  • Adds the recreate-all-service-instances errand. For more information, see Post-Deploy Errands.

Known Issues

This release has the following known issues:

  • The pre-provisioned broker does not terminate failed TCP connections when the request fails with a 4xx status code and when unbinding services. Over time, this can cause the file descriptor limit on the VMs that host HAProxy and the pre-provisioned broker to reach capacity:
    • When capacity is reached on the HAProxy VM, RabbitMQ is unreachable.
    • When capacity is reached on the pre-provisioned broker, app developers cannot create, bind, unbind, or delete service instances.
    To resolve the issue, do one of the following:
  • [Security Issue] The method for generating the Erlang cookie is not secure. For more information about this security issue, see CVE-2018-1279: RabbitMQ cluster compromise due to deterministically generated cookie.

  • An issue with service metrics causes zombie processes to accumulate on rabbitmq-server VMs. This can cause the VM to run out of resources and BOSH to restart it. If this occurs, Pivotal recommends that you stop the service-metrics job. However, if you stop the job, metrics will not be available.

  • Cluster scaling or changing the Erlang Cookie value requires cluster downtime, and might result in failed deployments. For more information, see Cluster Scaling Known Issue and Changing the Erlang Cookie Value Known Issue.

  • Changing networks or IP addresses for the RabbitMQ Server job results in a failed deployment. For more information, see Changing Network or IP Addresses Results in a Failed Deployment.

  • When errand run rules are set to When Changed, Ops Manager may not run the errands when the tile has relevant changes. For more information, see Managing Errands in Ops Manager. Pivotal recommends leaving the default run rule set to On.

  • There are issues with the configuration of pre-provisioned RabbitMQ with external load balancers.

  • Shareable instances are enabled in the Global Settings for On-Demand Plans tab for the pre-provisioned service as well as the on-demand service. For how to enable shareable instances, see Configure Global Settings.

Packages

  • OSS RabbitMQ v3.7.11
  • Erlang v20.3.8.18
  • HAProxy v1.8.17

v1.14.7

Release Date: February 13, 2019

Breaking Change: RabbitMQ for PCF v1.14 and later requires a Xenial stemcell. You must manually download and import a new stemcell into the Ops Manager Stemcell Library before deploying RabbitMQ for PCF v1.14. This might break automation you have set up to update RabbitMQ for PCF deployments that used Trusty stemcells. To download the Xenial stemcell from Pivotal Network, go to Stemcells for PCF (Ubuntu Xenial). For instructions on importing the stemcell, see Importing and Managing Stemcells.

Breaking Change: Syslog forwarding uses RFC5424 format, and the Legacy Format is no longer available. If you are upgrading and have Legacy Format selected in your existing syslog configuration, that setting is automatically reconfigured to use the RFC5424 format.

Features

New features and changes in this release:

  • Previously, when multiple Availability Zones (AZ) were selected for a single-node service plan, all instances of that plan would be deployed to the first AZ. Now the AZ is selected randomly from the configured list. This change does not affect existing instances and only applies to newly created instances.

Known Issues

This release has the following known issues:

Packages

  • OSS RabbitMQ v3.7.11
  • Erlang v20.3.8.18
  • HAProxy v1.8.17

v1.14.6

Release Date: December 28, 2018

Breaking Change: RabbitMQ for PCF v1.14 and later requires a Xenial stemcell. You must manually download and import a new stemcell into the Ops Manager Stemcell Library before deploying RabbitMQ for PCF v1.14. This might break automation you have set up to update RabbitMQ for PCF deployments that used Trusty stemcells. To download the Xenial stemcell from Pivotal Network, go to Stemcells for PCF (Ubuntu Xenial). For instructions on importing the stemcell, see Importing and Managing Stemcells.

Breaking Change: Syslog forwarding uses RFC5424 format, and the Legacy Format is no longer available. If you are upgrading and have Legacy Format selected in your existing syslog configuration, that setting is automatically reconfigured to use the RFC5424 format.

Features

New features and changes in this release:

Fixed Issue

This release fixes the following issue:

  • In RabbitMQ for PCF v1.14.5 and earlier, the maximum number of file descriptors was not set and this limited the maximum number of file descriptors used by RabbitMQ.

Known Issues

This release has the following known issues:

Packages

  • OSS RabbitMQ v3.7.9
  • Erlang v20.3.8.15
  • HAProxy v1.6.13

v1.14.5

Release Date: December 20, 2018

Breaking Change: RabbitMQ for PCF v1.14 and later requires a Xenial stemcell. You must manually download and import a new stemcell into the Ops Manager Stemcell Library before deploying RabbitMQ for PCF v1.14. This might break automation you have set up to update RabbitMQ for PCF deployments that used Trusty stemcells. To download the Xenial stemcell from Pivotal Network, go to Stemcells for PCF (Ubuntu Xenial). For instructions on importing the stemcell, see Importing and Managing Stemcells.

Breaking Change: Syslog forwarding uses RFC5424 format, and the Legacy Format is no longer available. If you are upgrading and have Legacy Format selected in your existing syslog configuration, that setting is automatically reconfigured to use the RFC5424 format.

Features

New features and changes in this release:

  • Fixed issue where RabbitMQ metrics were not visible on Loggregator Firehose after an upgrade
  • Set swap to 1 GB for RabbitMQ nodes
  • Supports the Log Cache cf CLI plugin that enables developers to access logs for an on-demand service instance using the command cf tail.

For more information about this feature, see Access RabbitMQ Metrics for On-Demand Service Instances.

Known Issues

This release has the following known issues:

Packages

  • OSS RabbitMQ v3.7.9
  • Erlang v20.3.8.15
  • HAProxy v1.6.13

v1.14.4

Release Date: November 22, 2018

Breaking Change: RabbitMQ for PCF v1.14 and later requires a Xenial stemcell. You must manually download and import a new stemcell into the Ops Manager Stemcell Library before deploying RabbitMQ for PCF v1.14. This might break automation you have set up to update RabbitMQ for PCF deployments that used Trusty stemcells. To download the Xenial stemcell from Pivotal Network, go to Stemcells for PCF (Ubuntu Xenial). For instructions on importing the stemcell, see Importing and Managing Stemcells.

Breaking Change: Syslog forwarding uses RFC5424 format, and the Legacy Format is no longer available. If you are upgrading and have Legacy Format selected in your existing syslog configuration, that setting is automatically reconfigured to use the RFC5424 format.

Security Fixes

This release includes the following security fix:

Features

New features and changes in this release:

  • Adds mutual TLS between service metrics and the Loggregator system
  • Removes credentials from the dashboard URL in the pre-provisioned service

Known Issues

This release has the following known issues:

Packages

  • OSS RabbitMQ v3.7.8
  • Erlang v20.3.8.10
  • HAProxy v1.6.13

v1.14.3

Release Date: November 1, 2018

Breaking Change: RabbitMQ for PCF v1.14 and later requires a Xenial stemcell. You must manually download and import a new stemcell into the Ops Manager Stemcell Library before deploying RabbitMQ for PCF v1.14. This might break automation you have set up to update RabbitMQ for PCF deployments that used Trusty stemcells. To download the Xenial stemcell from Pivotal Network, go to Stemcells for PCF (Ubuntu Xenial). For instructions on importing the stemcell, see Importing and Managing Stemcells.

Breaking Change: Syslog forwarding uses RFC5424 format, and the Legacy Format is no longer available. If you are upgrading and have Legacy Format selected in your existing syslog configuration, that setting is automatically reconfigured to use the RFC5424 format.

Features

New features and changes in this release:

  • Smoke tests are now more resilient when using external load balancers.

Known Issues

This release has the following known issues:

Packages

  • OSS RabbitMQ v3.7.8
  • Erlang v20.3.8.9
  • HAProxy v1.6.13

v1.14.1 - Withdrawn

Release Date: October 2, 2018

This release has been removed from Pivotal Network because of an issue with open source RabbitMQ v3.7.7.

Breaking Change: RabbitMQ for PCF v1.14 and later requires a Xenial stemcell. You must manually download and import a new stemcell into the Ops Manager Stemcell Library before deploying RabbitMQ for PCF v1.14. This might break automation you have set up to update RabbitMQ for PCF deployments that used Trusty stemcells. To download the Xenial stemcell from Pivotal Network, go to Stemcells for PCF (Ubuntu Xenial). For instructions on importing the stemcell, see Importing and Managing Stemcells.

Breaking Change: Syslog forwarding uses RFC5424 format, and the Legacy Format is no longer available. If you are upgrading and have Legacy Format selected in your existing syslog configuration, that setting is automatically reconfigured to use the RFC5424 format.

Features

New features and changes in this release:

  • The pre-provisioned RabbitMQ service is now optional. It is enabled by default for users who are upgrading from previous versions. It is disabled by default for all other users, but can be enabled in the configuration. For more information, see Turning Off the Pre-Provisioned Service. If you use RabbitMQ for PCF for Spring Cloud Services, you must turn on the pre-provisioned RabbitMQ Service.

  • The configuration tabs have been simplified to make it clearer which properties relate to the pre-provisioned service and which relate to the on-demand service.

  • On-Demand instances with TLS enabled use HTTPS instead of HTTP inside the PCF network.

  • RabbitMQ for PCF uses compiled BOSH releases, resulting in improved deployment times. However, you might still see some compilation when upgrading to v1.14. This is because if both compiled and source versions of the same BOSH release are available and the stemcell version used for deployment does not match the stemcell used for compilation, BOSH prefers to compile the source releases instead of using the compiled release.

  • RabbitMQ for PCF now uses floating stemcells. That means that RabbitMQ instances are recreated based on the new stemcell whenever a newer patch release of the stemcell becomes available. You can opt out of using a given stemcell version for any specific tile or deployment using OpsManager Stemcell Library.

Known Issues

This release has the following known issues:

Packages

  • OSS RabbitMQ v3.7.7
  • Erlang v20.3.8.1
  • HAProxy v1.6.13

View Release Notes for Another Version

To view the release notes for another product version, select the version from the dropdown at the top of this page.

Was this helpful?
What can we do to improve?