RabbitMQ® for PCF Release Notes

Note: This version of RabbitMQ for Pivotal Platform 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.14.x version, upgrade to the latest v1.14.x version before upgrading to the latest v1.15.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.15.13

Release Date: October 11, 2019

Security Fixes

This release includes the following security fixes:

  • Critical CVE-2019-9512: Some HTTP/2 implementations are vulnerable to ping floods, potentially leading to a denial of service. The attacker sends continual pings to an HTTP/2 peer, causing the peer to build an internal queue of responses. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.

  • Critical CVE-2019-9514: Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service. The attacker opens a number of streams and sends an invalid request over each stream that should solicit a stream of RST_STREAM frames from the peer. Depending on how the peer queues the RST_STREAM frames, this can consume excess memory, CPU, or both.

  • Critical CVE-2019-9515: Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.

  • The update to OSS RabbitMQ v3.7.18 includes a security fix. For more information about RabbitMQ v3.7.18, see the RabbitMQ Changelog.

Known Issues

This release has the following known issues:

Packages

  • OSS RabbitMQ v3.7.18 ⁠— Release notes
  • Erlang v20.3.8.22
  • HAProxy v1.8.21

v1.15.12

Release Date: August 27, 2019

Security Fix

This release includes the following security fix:

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.15.11

Release Date: June 14, 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.15.10

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.15.9

Release Date: May 17, 2019

Resolved Issue

This release fixes the following issue:

  • RabbitMQ for PCF v1.15.8. could fail to deploy on Pivotal Application Service (PAS) 2.4.4 and earlier. See v1.15.8 - Withdrawn below.

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.14
  • Erlang v20.3.8.20
  • HAProxy v1.8.19

v1.15.8 ⁠— Withdrawn

Release Date: May 3, 2019

This release has been removed from Pivotal Network because it can fail to deploy on PAS v2.4.4 and earlier. This issue is fixed in RabbitMQ for PCF v1.15.9.

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.15.7

Release Date: March 28, 2019

Resolved Issue

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.15.6

Release Date: March 14, 2019

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 can 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 might not run the errands when the tile has relevant changes.

  • 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.15.5

Release Date: March 11, 2019

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 can 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 might not run the errands when the tile has relevant changes.

  • 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.15.4

Release Date: February 13, 2019

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.15.3

Release Date: December 28, 2018

Features

New features and changes in this release:

Fixed Issue

This release fixes the following issue:

  • In RabbitMQ for PCF v1.15.2, 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.15.2

Release Date: December 20, 2018

Features

New features and changes in this release:

  • The “upgrade all service instances” errand defaults to upgrading in parallel. You can configure this using the Maximum number of instances upgraded in parallel field.

    For more information about this field, see Configure Global Settings.

  • Supports the Log Cache cf CLI plugin that enables developers to access logs for an on-demand service instance by running the command cf tail.

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

  • For on-demand service instances, the Erlang cookie and the RabbitMQ admin password are stored in the BOSH CredHub. This requires port 8844 on the BOSH Director to be accessible from the on-demand broker.

  • The rabbitmq_consistent_hash_exchange and rabbitmq_sharding plugins are enabled.

    For more information, see RabbitMQ Server Settings That Cannot Be Disabled.

  • Adds mutual TLS between service metrics and the Loggregator system.

  • Removes credentials from the dashboard URL in the pre-provisioned service.

  • The maximum number of on-demand services instances that can be deployed has been increased to 200.

  • Set swap to 1 GB for RabbitMQ nodes.

Known Issues

This release has the following known issues:

Packages

  • OSS RabbitMQ v3.7.9
  • Erlang v20.3.8.15
  • 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?