Shared Agents are not leased to controllers because the Operations Center Agent Provisioning Service is not configured

2 minute readKnowledge base

Issue

  • I use CasC, and, after upgrading my CloudBees CI cluster to 2.375.3.4 or later, I am unable to use shared agents in my jobs. The build keeps waiting for the next available executor or finds no nodes to schedule the task although the agent is shown as available in the Operations Center.

  • Shared agents are not leased to a new controller that was created at version 2.375.3.4 or higher. The builds in the controller keep waiting for the next available executor or find no nodes to schedule the task although the agent is shown as available in the Operations Center.

Environment

Context

For a controller to use shared agents, the Operations Center Cloud plugin must be installed on the controller. If the controller was installed with the "suggested plugins", then this plugin should be installed by default. However, before configuring shared agents in the operations center, it is prudent to verify that this plugin is installed on any controller that will use these shared agents provisioned by the operations center.

Fixed add and remove behavior of operations center cloud plugin (BEE-28432). This fix causes that the controller no longer adds or removes the cloud for the user. It will now display an administrative monitor if it is absent and the controller defines a connection to the operations center. If you are managing the configuration with CloudBees Configuration as Code (CasC), you will need to include the cloud explicitly in the clouds section of the jenkins.yaml file.

Resolution

  1. Make sure that the Operations Center Cloud plugin is installed and enabled in the controller.

  2. From the controller’s main dashboard, navigate to Manage Jenkins > Clouds.

  3. Add a new cloud of type Operations Center Agent Provisioning Service.

  4. (For CasC users only) Add operationsCenterAgentProvisioningService to the list of clouds in the controller’s bundle jenkins.yaml file and apply the bundle:

jenkins:
  clouds:
  - "operationsCenterAgentProvisioningService"
▼

If the issue persists, open a ticket to CloudBees Support explaining the situation, indicating the steps that have been followed and attaching a Support Bundle of the affected instances.

Tested product environment