Pivotal Knowledge Base


Pivotal Cloud Foundry RabbitMQ Smoke-Tests failing after changing or Adding Elastic Runtime Apps Domain


RabbitMQ for Pivotal Cloud Foundry 1.8.x and 1.9.0 - 1.9.5


PCF RabbitMQ smoke-tests errand is failing after changing/adding ERT apps domain.


If you change or add the ERT apps domain, this will change the default order of the shared apps domains in the output of command cf domains.

For example,

The default apps domain assigned during installation is apps.domain.example.com. If there is a requirement to add a different apps domain to run some apps, it can be added using the command:

$ cf create-shared-domain <DOMAIN>

In this used case, the default apps domain was deleted and re-added making the default apps domain listed below the newly added shared apps domain.

This will change the order of the cf domains output which now shows the example.com domain top of the list:

$ cf domains
name status type
example.com shared
apps.domain.example.com shared

The ERT smoke-tests errand will be successful as it uses the correct domain for verification and creating smoke-tests apps.

However, the rabbitmq smoke-tests errand will use the top of the list apps domain and will try to verify with the ERT default apps domain.

Due to this conflict in domain names, the rabbitmq smoke-tests fail with errors.

A closer look at the installation logs will reveal that the rabbitmq smoke-tests app is deployed with the top of the list apps domain. In this example: 

requested state: started
instances: 1/1
usage: 256M x 1 instances
urls: 0ecc5867-xxxx-xxxx-xxxx-aa56685793aa.example.com
last uploaded: Fri Jul 28 13:11:04 UTC 2017
stack: unknown
buildpack: ruby 1.6.39

state since cpu memory disk details
#0 running 2017-07-28 01:12:02 PM 0.0% 26.1M of 256M 89.1M of 1G

Further, it tries to verify the app by posting to the store of the app with default apps domain. In this example:

[2017-07-28 13:12:07.39 (UTC)]> curl -s -d myvalue -X POST https://0ecc5867-6b44-4c23-af24-aa56685793aa.apps.domain.example.com/store -k -f

This leads to a failure of the RabbitMQ smoke-tests errand.


The permanent fix is available in the latest version 1.9.6 and above of RabbitMQ for PCF. See RabbitMQ for PCF Release Notes for details.

Please contact Pivotal Support if this doesn't fix the issue.


Powered by Zendesk