⚠️ 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-1006

RemoteConfigDataInvalidSoloError — Configuration

RemoteConfigDataInvalidSoloError

CodeSOLO-1006
CategoryConfiguration
OwnershipInfrastructure
RetryableNo

Description

Thrown when the remote configuration stored in the solo-remote-config ConfigMap cannot be turned into a configuration object: the remote-config-data value is empty, is not parseable as YAML, or parses to something that is not a configuration object (a bare scalar, null, or a sequence). solo treats that ConfigMap as the source of truth for a deployment and reads it before almost any other work, so an unusable value blocks the whole command. The value is normally only written by solo itself, so this means it was hand-edited, truncated by a partial or interrupted write, or otherwise corrupted in the cluster. The offending value is captured on the error (meta.capturedData) so it can be inspected after the fact.

Troubleshooting Steps

  1. Inspect the stored value: kubectl get configmap solo-remote-config -n -o yaml
  2. The full captured value is recorded in ~/.solo/logs/solo.log
  3. Recover by deleting and recreating the cluster: solo one-shot single destroy, then solo one-shot single deploy
  4. Collect a diagnostics bundle: solo deployment diagnostics debug
  5. If this is reproducible or looks like a solo bug, open an issue or PR with the diagnostics bundle: https://github.com/hiero-ledger/solo/issues