Enabling OAUTH for RabbitMQ for TAS fails with syntax errors

Products

• VMware RabbitMQ

Issue/Introduction

You enabled OAUTH for RabbitMQ for TAS then you apply change. For OAUTH to be enabled on existing On Demand Service Instance. You ran upgrade-all-services errand.

The deployment fails with the following error:
 

[upgrade-all-service-instances] 2023/06/07 07:44:28.389444 canaries didn't process successfully: [01ac4302-642d-49e6-899d-9484564f16be] Operation failed: bosh task id 16769: Failed for bosh task: 16769  

Checking into the service instances deployment, rabbitmq-server vm is failing

$ bosh -d service-instance_01ac4302-642d-49e6-899d-9484564f16be vms
Instance Process State AZ IPs VM CID VM Type Active Stemcell
rabbitmq-server/5da19911-8c1b-4a61-8c61-e728697ac072 failing XX-AZ2 ###.##.###.## vm-ce683f28-e324-43ce-be39-f704e5f197b5 large true bosh-vsphere-esxi-ubuntu-jammy-go_agent/1.105

Checking into the /var/vcap/sys/logs/rabbitmq-server/startup_stdout.log, error below is thrown
 

Syntax error in /var/vcap/jobs/rabbitmq-server/etc/conf.d/13-oAuth.conf after line 5 column 1, parsing incomplete ----

Environment

Product Version: 2.1

Resolution

This is a known issue that is caused by a client secret that is empty and this is affecting RabbitMQ for TAS versions prior to version 2.2.5 and version 2.1.11

As a workaround

1.) SSH into the failing VM

bosh -d <service-instance-deployment> ssh <failing-rabbitmq-vm>

2.) edit OAUTH config

sudo vi /var/vcap/jobs/rabbitmq-server/etc/conf.d/13-oAuth.conf

3.) Change empty client_secret to a value '-'

management.oauth_client_secret = '-' 

4.) Restart failing jobs

monit start rabbitmq-server