SOLO-2004

DeploymentHasRemoteResourcesError

Description

Thrown when a deployment is deleted while it still has live components running in one of its clusters; the message names the deployment and the clusterReference where resources remain. Before removing a deployment’s local entry, solo checks each attached cluster and refuses to proceed if it still hosts components (mirror node, relay, explorer, block node, or the consensus network), since deleting the entry would orphan those running workloads. Destroy the components first, then delete the deployment.

Troubleshooting Steps

1. Destroy all components in the deployment before deleting it:
2. solo mirror node destroy
3. solo relay node destroy
4. solo explorer node destroy
5. solo block node destroy
6. solo consensus network destroy