Issue Summary

Loading the list of deployment environments inside the Bamboo admin > Agents > Remote agents > Online/ Offline > AGENT_NAME > Dedicate agent page can be extremely slow depending on the number of deployment environments that exist inside your Bamboo instance.

Steps to Reproduce

1. Go to Bamboo admin > Agents > Remote agents > Online/ Offline > AGENT_NAME > Dedicate agent page.
2. Select type Deployment environment.
3. Click the drop-down "Search for name" .

Expected Results

A list containing 25 deployment environments will show up in a matter of seconds.

Actual Results

Here's where it gets tricky. The page might end up loading depending on the number of deployment environments but the time can vary from a few seconds to several minutes. You might also encounter the following error message if you hit the reverse proxy/ load balancer timeout before Bamboo finishes gathering the list of deployment environments:

An unexpected error has occurred

Please try reloading the page.

This is mostly due to the fact that we're trying to fetch ALL deployment environments from the database at once. The results will be filtered out and you'll only see the top 25 because of the REST endpoint we're using the get that list:

• <Bamboo Base URL>/rest/api/latest/agent/assignment/search

We may only display 25 results in the UI but we're running a search against the database that gathers a list of ALL the deployment environments.

Workaround

There are a couple of workarounds available at the moment:

1. You can access the agents assignment page inside your deployment environment to dedicate an agent to it instead of going to the Bamboo admin > Agents > Remote agents > Online/ Offline > AGENT_NAME > Dedicate agent page. In short, access the deployment environment to dedicate the agent instead of going to the agent page to try and find the deployment environment in that list/ drop-down.
2. If you are hitting a timeout at the reverse proxy/ LB you may want to consider increasing the timeout.
   • Alternatively you can set up a Tomcat connector to bypass the reverse proxy/ LB and see how much time it takes to load the list of deployment environments. Once you know the time you can increase the reverse proxy/ LB timeout setting.