Bootstrap Workload Exists

URI: https://docs.ankatech.co/errors/bootstrap-workload-exists
HTTP Status: 409 Conflict

When you see this

The environment host asked to register the first platform administrative workload (envctl.sh <env> workload-bootstrap, operation createBootstrapPlatformWorkload), and a platform workload that is not REVOKED already exists — a SUSPENDED one included. Nothing was registered. See Administrative Workload Identity^*.

Common Causes

• The bootstrap was already run on this environment.
• A platform administrator has registered a platform workload in the console or through createPlatformWorkload.
• The only platform workload is suspended. Suspension does not reopen the bootstrap: the workload is reactivated, or revoked first.

Response Example

{
  "type": "https://docs.ankatech.co/errors/bootstrap-workload-exists",
  "title": "Bootstrap Workload Exists",
  "status": 409,
  "detail": "A platform administrative workload that is not revoked already exists, so the bootstrap registered nothing. A platform administrator registers further workloads with createPlatformWorkload.",
  "instance": "/api/v3/admin/platform/setup/workload-bootstrap",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

How to Resolve

1. Use the existing platform workload, or have a platform administrator register a new one with createPlatformWorkload and give it a key and scopes.
2. If the existing workload is suspended, reactivate it. A platform administrator reactivates it from the console when the administrator holds every scope it holds. In a development deployment (create-env.sh --app-env dev) the platform automation workload holds tenant-plane scopes no platform administrator holds, so the console cannot reactivate it there; recover it from the environment host with sudo envctl.sh <env> workload-recovery, which reactivates it under a new key.
3. envctl.sh removed the key file it generated for this run; no cleanup is needed on the host.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.