Redis enterprise broker_registrar errand fails to authenticate
Article ID: 404074
Updated On:
Products
Issue/Introduction
The errand broker_registrar fails with EOF error when trying to authenticate to cf api. You may observe error such as shown below:
Stdout cf version 6.34.1+bbdf81482.2018-01-17
Setting api endpoint to [36;1mhttps://api.domain-example.com[0m...
[32;1mOK[0m
api endpoint: https://api.domain-example.com
api version: 2.256.0
API endpoint: [36;1mhttps://api.domain-example.com[0m
Authenticating...
[31;1mFAILED[0m
...
+ BROKER_NAME=redislabs-broker-v2
+ BROKER_SERVICE_NAME=redislabs-v2
+ BROKER_URL=https://broker-redis-v2.domain-example.com
+ BROKER_USERNAME=********
+ BROKER_PASSWORD=********
+ SKIP_SSL_VALIDATION=
+ cf --version
+ cf api https://api.domain-example.com
+ cf auth system_services ********
Post https://login.domain-example.com/oauth/token: EOF As seen from the error, login fails to the broker with URL specified.
Environment
Redis enterprise
Cause
The issue occurs when there are multiple broker defined in the environment. In this case it was observed the tile configuration in Redis Enterprise --> Routing section would point to url broker-redis-v2.domain-example.com, however the actual broker name used in the environment was broker-redis-v3.domain-example.com.
Use cf service-brokers command to check the brokers running in the environment and confirm a single broker is running for this service.
Resolution
If you observe 2 brokers running in the environment and errand failing with EOF, please open ticket with Broadcom support to review the configuration and fix the issue.
Feedback
