RabbitMQ® for PCF Release Notes

Note: RabbitMQ for Pivotal Cloud Foundry v1.13 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

Warning: You must follow the upgrade procedure described in Upgrade the RabbitMQ for Pivotal Cloud Foundry Pre-Provisioned Service to successfully upgrade from RabbitMQ for PCF v1.12 to v1.13. If you do not follow the procedure, you will experience prolonged downtime and might experience data loss.

Warning: Pivotal requires you to upgrade to the latest 1.12.x, and then move to the latest available 1.13.x. Failing to do this can result in prolonged downtime or data loss.

For more on 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.13.20

Release Date: May 20, 2019

Features

New features and changes in this release:

  • Requires Ubuntu Trusty stemcell 3586.100.
  • 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:
  • When you upgrade from RabbitMQ v3.6 to v3.7, a directory might be created. This causes issues after the service is restarted. For information on how to resolve this issue, see Prerequisite in Upgrading RabbitMQ for Pivotal Cloud Foundry.

Packages

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

v1.13.18

Release Date: March 28, 2019

Features

New features and changes in this release:

  • Requires Ubuntu Trusty stemcell 3586.91.

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

  • You cannot upgrade from RabbitMQ for PCF v1.12 to v1.13 on PCF v2.2.0 - v2.2.5. You must upgrade on PCF v2.2.6 or later.

  • If you are upgrading RabbitMQ for PCF v1.12 to v1.13 and you use Spring Cloud Services, you must disable all errands in the Spring Cloud Services tile during the upgrade to ensure that the upgrade succeeds.

  • Cluster scaling or changing the Erlang cookie value requires cluster downtime and might result in failed deployments. For more information, see Erlang Cookie, 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. Pivotal recommends leaving the default run rule set to On. For more information, see Managing Errands in Ops Manager.

  • When you upgrade from RabbitMQ v3.6 to v3.7, a directory might be created. This causes issues after the service is restarted. For information on how to resolve this issue, see Prerequisite in Upgrading RabbitMQ for Pivotal Cloud Foundry.

Packages

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

v1.13.17

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.

  • You cannot upgrade from RabbitMQ for PCF v1.12 to v1.13 on PCF v2.2.0 - v2.2.5. You must upgrade on PCF v2.2.6 or later.

  • If you are upgrading RabbitMQ for PCF v1.12 to v1.13 and you use Spring Cloud Services, you must disable all errands in the Spring Cloud Services tile during the upgrade to ensure that the upgrade succeeds.

  • Cluster scaling or changing the Erlang cookie value requires cluster downtime and might result in failed deployments. For more information, see Erlang Cookie, 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. Pivotal recommends leaving the default run rule set to On. For more information, see Managing Errands in Ops Manager.

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

  • When you upgrade from RabbitMQ v3.6 to v3.7, a directory might be created. This causes issues after the service is restarted. For information on how to resolve this issue, see Prerequisite in Upgrading RabbitMQ for Pivotal Cloud Foundry.

Packages

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

v1.13.16

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.

  • Requires Ubuntu Trusty stemcell 3586.86.

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.

  • You cannot upgrade from RabbitMQ for PCF v1.12 to v1.13 on PCF v2.2.0 - v2.2.5. You must upgrade on PCF v2.2.6 or later.

  • If you are upgrading RabbitMQ for PCF v1.12 to v1.13 and you use Spring Cloud Services, you must disable all errands in the Spring Cloud Services tile during the upgrade to ensure that the upgrade succeeds.

  • Cluster scaling or changing the Erlang cookie value requires cluster downtime and might result in failed deployments. For more information, see Erlang Cookie, 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. Pivotal recommends leaving the default run rule set to On. For more information, see Managing Errands in Ops Manager.

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

  • When you upgrade from RabbitMQ v3.6 to v3.7, a directory might be created. This causes issues after the service is restarted. For information on how to resolve this issue, see Prerequisite in Upgrading RabbitMQ for Pivotal Cloud Foundry.

Packages

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

v1.13.15

Release Date: February 18, 2019

Features

New features and changes in this release:

  • BOSH Process Manager downgraded to 1.0.2 to resolve the issue introduced in RabbitMQ for PCF 1.13.14
  • Requires stemcell 3586.79

Known Issues

This release has the following known issues:

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

  • You cannot upgrade from RabbitMQ for PCF v1.12 to v1.13 on PCF v2.2.0 - v2.2.5. You must upgrade on PCF v2.2.6 or later.

  • If you are upgrading RabbitMQ for PCF v1.12 to v1.13 and you use Spring Cloud Services, you must disable all errands in the Spring Cloud Services tile during the upgrade to ensure that the upgrade succeeds.

  • Cluster scaling or changing the Erlang cookie value requires cluster downtime and might result in failed deployments. For more information, see Erlang Cookie, 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. Pivotal recommends leaving the default run rule set to On. For more information, see Managing Errands in Ops Manager.

  • When you upgrade from RabbitMQ v3.6 to v3.7, a directory might be created. This causes issues after the service is restarted. For information on how to resolve this issue, see Prerequisite in Upgrading RabbitMQ for Pivotal Cloud Foundry.

Packages

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

v1.13.14 - Withdrawn

Release Date: February 14, 2019

This release has been removed from Pivotal Network because of incompatibility between the following:

  • BOSH Process Manager (BPM) v1.0.3 and later
  • Trusty stemcells v3586.71 and later
  • Dynatrace Full-Stack Add-on for PCF, all versions

This issue has been fixed in RabbitMQ for PCF 1.13.15.

Features

New features and changes in this release:

  • Requires stemcell 3586.71
  • Previously, when multiple Availability Zones (AZ) were selected for a single-node service plan, all instances of that plan were 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:

  • When you upgrade from RabbitMQ v3.6 to v3.7, a directory might be created. This causes issues after the service is restarted. For information on how to resolve this issue, see Prerequisite in Upgrading RabbitMQ for Pivotal Cloud Foundry.

Packages

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

v1.13.13

Release Date: December 28, 2018

Features

New features and changes in this release:

Known Issues

This release has the following known issues:

  • [Security Issue] There is a issue related to BPM v1.0.2 and earlier. RabbitMQ for Pivotal Cloud Foundry v1.13 cannot use BPM v1.0.3. To resolve this issue, upgrade to RabbitMQ for Pivotal Cloud Foundry v1.14.
  • You cannot upgrade from RabbitMQ for PCF v1.12 to v1.13 on PCF v2.2.0 - v2.2.5. You must upgrade on PCF v2.2.6 or later.

  • If you are upgrading RabbitMQ for PCF v1.12 to v1.13 and you use Spring Cloud Services, you must disable all errands in the Spring Cloud Services tile during the upgrade to ensure that the upgrade succeeds.

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

  • Changing networks and/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. Pivotal recommends leaving the default run rule set to On. For more information, see Managing Errands in Ops Manager.

  • When you upgrade from RabbitMQ v3.6 to v3.7, a directory might be created. This causes issues after the service is restarted. For information on how to resolve this issue, see Prerequisite in Upgrading RabbitMQ for Pivotal Cloud Foundry.

Packages

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

v1.13.12

Release Date: December 20, 2018

Features

New features and changes in this release:

  • PCF v2.1 is no longer supported
  • Fixed issue where RabbitMQ metrics were not visible on the Loggregator Firehose after an upgrade
  • Requires stemcell 3586.60
  • 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:

  • [Security Issue] There is a issue related to BPM v1.0.2 and earlier. RabbitMQ for Pivotal Cloud Foundry v1.13 cannot use BPM v1.0.3. To resolve this issue, upgrade to RabbitMQ for Pivotal Cloud Foundry v1.14.
  • You cannot upgrade from RabbitMQ for PCF v1.12 to v1.13 on PCF v2.2.0 - v2.2.5. You must upgrade on PCF v2.2.6 or later.

  • If you are upgrading RabbitMQ for PCF v1.12 to v1.13 and you use Spring Cloud Services, you must disable all errands in the Spring Cloud Services tile during the upgrade to ensure that the upgrade succeeds.

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

  • Changing networks and/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. Pivotal recommends leaving the default run rule set to On. For more information, see Managing Errands in Ops Manager.

  • When you upgrade from RabbitMQ v3.6 to v3.7, a directory might be created. This causes issues after the service is restarted. For information on how to resolve this issue, see Prerequisite in Upgrading RabbitMQ for Pivotal Cloud Foundry.

Packages

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

v1.13.11

Release Date: November 22, 2018

Security Fixes

This release includes the following security fix:

Features

New features and changes in this release:

  • Requires stemcell 3586.57
  • 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:

  • [Security Issue] There is a issue related to BPM v1.0.2 and earlier. RabbitMQ for Pivotal Cloud Foundry v1.13 cannot use BPM v1.0.3. To resolve this issue, upgrade to RabbitMQ for Pivotal Cloud Foundry v1.14.
  • You cannot upgrade from RabbitMQ for PCF v1.12 to v1.13 on PCF v2.2.0 - v2.2.5. You must upgrade on PCF v2.1 or on PCF v2.2.6 or later.

  • If you are upgrading RabbitMQ for PCF v1.12 to v1.13 and you use Spring Cloud Services, you must disable all errands in the Spring Cloud Services tile during the upgrade to ensure that the upgrade succeeds.

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

  • Changing networks and/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. Pivotal recommends leaving the default run rule set to On. For more information, see Managing Errands in Ops Manager.

  • When you upgrade from RabbitMQ v3.6 to v3.7, a directory might be created. This causes issues after the service is restarted. For information on how to resolve this issue, see Prerequisite in Upgrading RabbitMQ for Pivotal Cloud Foundry.

Packages

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

v1.13.10

Release Date: November 1, 2018

Features

New features and changes in this release:

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

Known Issues

This release has the following known issues:

  • [Security Issue] There is a issue related to BPM v1.0.2 and earlier. RabbitMQ for Pivotal Cloud Foundry v1.13 cannot use BPM v1.0.3. To resolve this issue, upgrade to RabbitMQ for Pivotal Cloud Foundry v1.14.
  • You cannot upgrade from RabbitMQ for PCF v1.12 to v1.13 on PCF v2.2.0 - v2.2.5. You must upgrade on PCF v2.1 or on PCF v2.2.6 or later.

  • If you are upgrading RabbitMQ for PCF v1.12 to v1.13 and you use Spring Cloud Services, you must disable all errands in the Spring Cloud Services tile during the upgrade to ensure that the upgrade succeeds.

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

  • Changing networks and/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. Pivotal recommends leaving the default run rule set to On. For more information, see Managing Errands in Ops Manager.

  • When you upgrade from RabbitMQ v3.6 to v3.7, a directory might be created. This causes issues after the service is restarted. For information on how to resolve this issue, see Prerequisite in Upgrading RabbitMQ for Pivotal Cloud Foundry.

Packages

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

v1.13.8

Release Date: October 5, 2018

Features

Changes in this release:

  • Requires stemcell 3586.46
  • RabbitMQ updated to 3.7.8
  • Erlang updated to v20.3.8.9

Known Issues

This release has the following known issues:

  • [Security Issue] There is a issue related to BPM v1.0.2 and earlier. RabbitMQ for Pivotal Cloud Foundry v1.13 cannot use BPM v1.0.3. To resolve this issue, upgrade to RabbitMQ for Pivotal Cloud Foundry v1.14.
  • You cannot upgrade from RabbitMQ for PCF v1.12 to v1.13 on PCF v2.2.0 - v2.2.5. You must upgrade on PCF v2.1 or on PCF v2.2.6 or later.

  • If you are upgrading RabbitMQ for PCF v1.12 to v1.13 and you use Spring Cloud Services, you must disable all errands in the Spring Cloud Services tile during the upgrade to ensure that the upgrade succeeds.

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

  • Changing networks and/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. Pivotal recommends leaving the default run rule set to On. For more information, see Managing Errands in Ops Manager.

  • When you upgrade from RabbitMQ v3.6 to v3.7, a directory might be created. This causes issues after the service is restarted. For information on how to resolve this issue, see Prerequisite in Upgrading RabbitMQ for Pivotal Cloud Foundry.

Packages

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

v1.13.7 - Withdrawn

Release Date: September 13, 2018

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

Features

New features and changes in this release:

  • Requires stemcell 3586.42
  • Smoke tests now wait up to 5 minutes for a test app to deploy.

Known Issues

This release has the following known issues:

  • [Security Issue] There is a issue related to BPM v1.0.2 and earlier. RabbitMQ for Pivotal Cloud Foundry v1.13 cannot use BPM v1.0.3. To resolve this issue, upgrade to RabbitMQ for Pivotal Cloud Foundry v1.14.
  • You cannot upgrade from RabbitMQ for PCF v1.12 to v1.13 on PCF v2.2.0 - v2.2.5. You must upgrade on PCF v2.1 or on PCF v2.2.6 or later.

  • If you are upgrading RabbitMQ for PCF v1.12 to v1.13 and you use Spring Cloud Services, you must disable all errands in the Spring Cloud Services tile during the upgrade to ensure that the upgrade succeeds.

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

  • Changing networks and/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. Pivotal recommends leaving the default run rule set to On. For more information, see Managing Errands in Ops Manager.

  • When you upgrade from RabbitMQ v3.6 to v3.7, a directory might be created. This causes issues after the service is restarted. For information on how to resolve this issue, see Prerequisite in Upgrading RabbitMQ for Pivotal Cloud Foundry.

Packages

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

v1.13.3 - Withdrawn

Release Date: August 20, 2018

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

Features

Change in this release:

Known Issues

This release has the following known issues:

  • [Security Issue] There is a issue related to BPM v1.0.2 and earlier. RabbitMQ for Pivotal Cloud Foundry v1.13 cannot use BPM v1.0.3. To resolve this issue, upgrade to RabbitMQ for Pivotal Cloud Foundry v1.14.
  • You cannot upgrade from RabbitMQ for PCF v1.12 to v1.13 on PCF v2.2.0 - v2.2.5. You must upgrade on PCF v2.1 or on PCF v2.2.6 or later.

  • If you are upgrading RabbitMQ for PCF v1.12 to v1.13 and you use Spring Cloud Services, you must disable all errands in the Spring Cloud Services tile during the upgrade to ensure that the upgrade succeeds.

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

  • Changing networks and/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. Pivotal recommends leaving the default run rule set to On. For more information, see Managing Errands in Ops Manager.

  • When you upgrade from RabbitMQ v3.6 to v3.7, a directory might be created. This causes issues after the service is restarted. For information on how to resolve this issue, see Prerequisite in Upgrading RabbitMQ for Pivotal Cloud Foundry.

Packages

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

v1.13.2 - Withdrawn

Release Date: August 3, 2018

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

Features

New features and changes in this release:

  • VCAP_SERVICES now contains the correct port when TLS is enabled for an on-demand instance
  • On-demand smoke tests now time out after one hour
  • Stemcell updated to 3586.26

Known Issues

This release has the following known issues:

  • [Security Issue] There is a issue related to BPM v1.0.2 and earlier. RabbitMQ for Pivotal Cloud Foundry v1.13 cannot use BPM v1.0.3. To resolve this issue, upgrade to RabbitMQ for Pivotal Cloud Foundry v1.14.
  • You cannot upgrade from RabbitMQ for PCF v.12 to v1.13 on PCF v2.2.0 - v2.2.5. You must upgrade on PCF v2.1 or on PCF v2.2.6 or later.

  • If you are upgrading RabbitMQ for PCF v1.12 to v1.13 and you use Spring Cloud Services, you must disable all errands in the Spring Cloud Services tile during the upgrade to ensure that the upgrade succeeds.

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

  • Changing networks and/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. Pivotal recommends leaving the default run rule set to On. For more information, see Managing Errands in Ops Manager.

  • When you upgrade from RabbitMQ v3.6 to v3.7, a directory might be created. This causes issues after the service is restarted. For information on how to resolve this issue, see Prerequisite in Upgrading RabbitMQ for Pivotal Cloud Foundry.

Packages

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

v1.13.0 - Withdrawn

Release Date: July 20, 2018

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

Features

New features and changes in this release:

  • Supports securing communication between apps and on-demand service instances using Transport Layer Security (TLS). For more information, see Preparing for TLS. For ease of upgrade from previous versions, this functionality is turned off by default.

  • Includes open source RabbitMQ v3.7. This version includes many improvements. For information about what is new in RabbitMQ v3.7, see the RabbitMQ documentation. The path to upgrade the pre-provisioned service to v3.7 requires manual intervention, and the path to upgrade the on-demand service requires removing preexisting instances. For information, see Upgrading RabbitMQ for PCF.

  • Smoke tests for the on-demand broker now use the system org, as is already the case for multi-tenant.

Known Issues

This release has the following known issues:

  • [Security Issue] There is a issue related to BPM v1.0.2 and earlier. RabbitMQ for Pivotal Cloud Foundry v1.13 cannot use BPM v1.0.3. To resolve this issue, upgrade to RabbitMQ for Pivotal Cloud Foundry v1.14.
  • You cannot upgrade from PCF v.12 to PCF v1.13 on PCF v2.2.0 - v2.2.5. You must upgrade on PCF v2.1 or on PCF v2.2.6 or later.

  • If you are upgrading RabbitMQ for PCF v1.12 to v1.13 and you use Spring Cloud Services, you must disable all errands in the Spring Cloud Services tile during the upgrade to ensure that the upgrade succeeds.

  • Cluster scaling or changing the Erlang Cookie value require 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 and/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.

  • When on-demand service instances are enabled for TLS, the port property in VCAP_SERVICES for amqp+ssl incorrectly reports that the port is 5672. The actual port used for amqp+ssl is 5671.

  • When you upgrade from RabbitMQ v3.6 to v3.7, a directory might be created. This causes issues after the service is restarted. For information on how to resolve this issue, see Prerequisite in Upgrading RabbitMQ for Pivotal Cloud Foundry.

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?