VMware Tanzu RabbitMQ for VMs Release Notes

Note: Pivotal Platform is now part of VMware Tanzu. In v1.20 and later, VMware Tanzu RabbitMQ [VMs] is named VMware Tanzu RabbitMQ for VMs.

For product versions and upgrade paths, see Upgrade Planner.

v1.20.3

Release Date: December 14, 2020

Features

New features and changes in this release:

• Option to limit the TLS versions enabled for on-demand instances: Tanzu RabbitMQ v1.21.0 supports TLS v1.0, v1.1, and v1.2 (default). Additionally, you can now select the TLS versions to enable in RabbitMQ. This disables the other TLS versions.
  To configure TLS, follow the procedure in Configure Security.
  For more information about disabling TLS versions, see the RabbitMQ documentation.

• Option to add VM extensions to on-demand instances: You can provide a list of VM extensions to add to on-demand service instances. This feature enables you to exclude VMs hosting on-demand service instances from being dynamically provisioned by an underlying IaaS, among other capabilities. For more information, see Configure Global Settings in Installing and Configuring the On-Demand Service.

• Includes the UAA URL in service keys and bindings when OAuth is enabled: This helps apps to fetch the OAuth token from UAA.

• Improved internal security for service-gateway: For delete operations, the on-demand service broker now communicates with routing components over mutual TLS.

Known Issues

This release has the following issue:

• Changing the Erlang cookie can cause failed deployments: Changing the Erlang cookie value requires cluster downtime and can result in failed deployments. For more information, see Changing the Erlang Cookie Value Known Issue.

• The direct reply-to feature is not supported: For on-demand service instances created in Tanzu RabbitMQ v1.20.0 and v1.21.0, the direct reply-to feature is not supported. For more information about the direct reply-to feature, see the RabbitMQ documentation.

Compatibility

The following components are compatible with this release:

^* For more information, see the v3.8.9 GitHub documentation.

v1.20.2

Release Date: October 21, 2020

Resolved Issues

This release has the following fix:

• rabbitmq-server-metrics BOSH job did not provide memory and disk metrics: This issue affected on-demand service instances created in v1.20.0 and v1.20.1 but is fixed when you upgrade these service instances to v1.20.2.

Known Issues

This release has the following issue:

• Changing the Erlang cookie can cause failed deployments: Changing the Erlang cookie value requires cluster downtime and can result in failed deployments. For more information, see Changing the Erlang Cookie Value Known Issue.

• The direct reply-to feature is not supported: For on-demand service instances created in Tanzu RabbitMQ v1.20.0 and v1.21.0, the direct reply-to feature is not supported. For more information about the direct reply-to feature, see the RabbitMQ documentation.

Compatibility

The following components are compatible with this release:

^* For more information, see the v3.8.9 GitHub documentation.

v1.20.1

Release Date: September 23, 2020

Features

New features and changes in this release:

• Erlang: Upgraded to v23.0.3.

Resolved Issues

This release has the following fixes:

• The on-demand adapter cleanly exits the drain script when the credentials are not present in UAA: The drain script now has the correct output for success (0) and failure (non-zero).

• Accessing the RabbitMQ Management UI: You can now access the RabbitMQ Management UI using OAuth2 with a SAML identity provider.

Known Issues

This release has the following known issues:

• Changing the Erlang cookie can cause failed deployments: Changing the Erlang cookie value requires cluster downtime and can result in failed deployments. For more information, see Changing the Erlang Cookie Value Known Issue.

• The direct reply-to feature is not supported: For on-demand service instances created in Tanzu RabbitMQ v1.20.0 and v1.21.0, the direct reply-to feature is not supported. For more information about the direct reply-to feature, see the RabbitMQ documentation.

• rabbitmq-server-metrics BOSH job does not provide memory and disk metrics: For on-demand service instances created in v1.20.0 and v1.20.1, the rabbitmq-server-metrics BOSH job does not provide memory and disk metrics. The following error messsage appears in /var/vcap/data/sys/log/service-metrics/rabbitmq-server-metrics.log:

    "source":"rabbitmq-server-metrics","message":"rabbitmq-server-metrics.metrics-fetching-failed","log_level":2,"data":{"error":"GetNode: Error 500 from RabbitMQ: EOF","provider":"APIProvider"}
  

  and the following error message in /var/vcap/data/sys/log/rabbitmq-server/rabbit@<BOSH DNS name>.log:

    [error]  CRASH REPORT Process  with 0 neighbours crashed with reason: {function_clause,[]}
  

Compatibility

The following components are compatible with this release:

^* For more information, see the v3.8.8 GitHub documentation.

v1.20.0

Release Date: August 21, 2020

Features

New features in this release:

• Syslog forwarding: Ops Manager now manages Tanzu RabbitMQ syslog configuration. This improvement does not affect syslog configuration for within the tile. However, for new service instances the default program name is different. To learn how to configure syslog to keep the log format consistent, see Configure Syslog Forwarding

• BOSH Hot Swap: To reduce downtime, on-demand service instances created using Tanzu RabbitMQ v1.20 and later use the vm_strategy create-swap-delete. During deployment, IaaS resource usage surges while BOSH creates additional VMs to prepare for the update. You might need to review resource limits for your IaaS and account. If your limits are too low, your deployment fails.
  On-demand service instances that were created using Tanzu RabbitMQ v1.19 or earlier and upgraded to v1.20 or later continue to use the vm_strategy delete-create.
  For more information about how this affects downtime, see BOSH Hot Swap.

• Individual service instance upgrades: Developers can upgrade Tanzu RabbitMQ on-demand service instances individually using the Cloud Foundry Command Line Interface (cf CLI). For more information about this feature, see About Individual Service Instance Upgrades. For instructions for individually upgrading service instances, see Upgrade an Individual Service Instance.

• OAuth: Support for the RabbitMQ OAuth plugin has now arrived in Tanzu RabbitMQ. Users can authenticate with the RabbitMQ Management UI through JWT-encoded OAuth 2.0 access tokens. For more information about the plugin, see rabbitmq-auth-backend-oauth2 in GitHub. For how to enable OAuth in Tanzu RabbitMQ, see Enabling OAuth for RabbitMQ.

Known Issues

This release has the following known issues:

• The on-demand adapter does not cleanly exit the drain script when the credentials are not present in UAA. The drain script is expected to output an integer to determine success (0) or failure (non-zero). In some cases, the drain script outputs errors even though the operation has succeeded. This causes a failure in the drain operation. This is fixed in v1.20.1.

• Accessing the RabbitMQ Management UI: If you are using OAuth2 with a SAML identity provider, you cannot access the RabbitMQ Management UI. This is fixed in v1.20.1 and later.

• rabbitmq-server-metrics BOSH job does not provide memory and disk metrics: For on-demand service instances created in v1.20.0 and v1.20.1, the rabbitmq-server-metrics BOSH job does not provide memory and disk metrics. The following error messsage appears in /var/vcap/data/sys/log/service-metrics/rabbitmq-server-metrics.log:

    "source":"rabbitmq-server-metrics","message":"rabbitmq-server-metrics.metrics-fetching-failed","log_level":2,"data":{"error":"GetNode: Error 500 from RabbitMQ: EOF","provider":"APIProvider"}
  

  and the following error message in /var/vcap/data/sys/log/rabbitmq-server/rabbit@<BOSH DNS name>.log:

    [error]  CRASH REPORT Process  with 0 neighbours crashed with reason: {function_clause,[]}
  

• Changing the Erlang cookie can cause failed deployments: Changing the Erlang cookie value requires cluster downtime and can result in failed deployments. For more information, see Changing the Erlang Cookie Value Known Issue.

• The direct reply-to feature is not supported: For on-demand service instances created in Tanzu RabbitMQ v1.20.0 and v1.21.0, the direct reply-to feature is not supported. For more information about the direct reply-to feature, see the RabbitMQ documentation.

Compatibility

The following components are compatible with this release:

^* For more information, see the v3.8.5 GitHub documentation.

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.