No agent serves the deployment

What it means#

The deployment has nowhere to run. Either no agent may run it, or every agent it was placed on is offline, so the integration doesn’t run in this environment.

What raises it#

The deployment is waiting and none of the agents it is placed on is online. A new installation gets two minutes for its first agents to report before the problem shows. The detail gives the cause nearest to placement first: an agent that serves the environment and meets the requirements may not run the project, the matching agents are draining, no agent that serves the environment meets the integration’s requirements, or no agent serves the environment at all. When the agents it’s placed on are offline, the detail lists them.

What to check#

See why the deployment is pending:

$ weikio status <project>/<integration> --env <environment>

List the agents that serve the environment, with their status and capabilities:

$ weikio get agents --env <environment>

Read the environment’s agents and its deployment counts per project:

$ weikio describe environment <environment>

How to fix it#

Start an offline agent on its site, or fix what the detail names. A platform administrator lets an agent run the project, stops draining it or gives it the capabilities the integration requires:

$ weikio agent set-projects <agent> <project>,<other-project>
$ weikio agent undrain <agent>
$ weikio agent set-capabilities <agent> os=linux environment=<environment>

set-projects and set-capabilities replace the agent’s whole list, so give every project and capability it should keep. When no agent serves the environment yet, enrol one with weikio agent enrol.