⚠️ Homebrew support is being deprecated. Solo will stop publishing updates to Homebrew after August 31, 2026. Install via npm install -g @hiero-ledger/solo@latest instead. See System Readiness for full install instructions.

SOLO-2029

BlockNodeClusterContextNotFoundSoloError — Deployment

BlockNodeClusterContextNotFoundSoloError

CodeSOLO-2029
CategoryDeployment
OwnershipUser
RetryableNo

Description

Thrown when solo needs to act on a block node but cannot determine which cluster (kubeconfig context) it lives in; the message names the blockNodeId. solo maps each block node to a registered cluster reference to find the context for its operations, so this is raised when no such mapping resolves — typically because the block node is not associated with a registered cluster reference, or the referenced cluster is missing from the deployment configuration.

Troubleshooting Steps

  1. List registered cluster references: solo cluster-ref config list
  2. Verify the block node is associated with a registered cluster
  3. Check deployment configuration: solo deployment config info