RabbitMQ Smoke Test exceeds 60 minutes and fails due to timeout

Products

• VMware RabbitMQ

Issue/Introduction

When running the On Demand Smoke test for RabbitMQ, to smoke test will fail if it exceeds 1 hour. This can happen when a large number of plans have been configured on the platform, as the smoke test will test each of these plans.

An indication that you have hit this issue is the following message at the end of the smoke test:
 

           Ginkgo ran 1 suite in 1h0m21.75828024s  

If this time exceeds one hour, the smoke test fails.

Environment

Product Version: 2.1

Resolution

This has been fixed in the following versions of RabbitMQ:

• 2.3.2+
• 2.2.10+

This fix involved running the Smoke test in parallel, performing the testing for multiple plans at the same time. Please note, this parallel feature is dependent on the number of CPUs of the Broker VM. A minimum of 2 CPUs is required to make use of this function.