SOLO-3022

ExplorerDeployFailedSoloError — Component

ExplorerDeployFailedSoloError

CodeSOLO-3022
CategoryComponent
OwnershipInfrastructure
RetryableNo

Description

Thrown when solo explorer node add cannot bring up the Hiero Explorer: the Helm release for the explorer chart failed to install, or its pods never reached a Ready state before solo stopped waiting. The original failure is wrapped in cause.message. Typical roots are an explorer image that cannot be pulled, misconfigured chart values (for example an unreachable mirror-node endpoint), a TLS/cert-manager prerequisite that is not ready, or insufficient cluster resources to schedule the pod.

Troubleshooting Steps

  1. Check solo logs: tail -n 100 ~/.solo/logs/solo.log
  2. Inspect explorer pods: kubectl get pods -A -l app.kubernetes.io/component=hiero-explorer
  3. Inspect Helm release: helm status -n