LATEST VERSION: 1.15 - RELEASE NOTES

RabbitMQ® for PCF Release Notes

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 will 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.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:

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:

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

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

Create a pull request or raise an issue on the source for this page in GitHub