| Previous | Next |
| ERROR_VMCOMPUTE_SYSTEM_NOT_FOUND | ERROR_VMCOMPUTE_SYSTEM_ALREADY_STOPPED |
ERROR_VMCOMPUTE_SYSTEM_ALREADY_EXISTS
A compute-system ID is a uniqueness boundary inside HCS
ERROR_VMCOMPUTE_SYSTEM_ALREADY_EXISTS occurs when creation uses an identifier already assigned to a live or not-yet-cleaned compute system. The conflict can result from duplicate orchestration requests, incomplete teardown, deterministic ID reuse or two controllers managing the same workload.
Generating a random replacement ID may hide the race and create duplicate workloads. The correct response depends on whether the existing system is the intended instance, an abandoned object or a concurrently created system owned by another request.
Evidence and corrective action
- Open or enumerate the existing compute system and inspect its owner, type and lifecycle state.
- Correlate creation attempts by request ID so retries do not create parallel systems.
- Wait for asynchronous termination and cleanup to finish before reusing a deterministic identifier.
- Use a single authoritative controller for create/delete decisions.
- Remove an existing system only after proving it is stale and not serving the intended workload.
References
Looking for a different code? Search another status or error code.