SOLO-4060

ServiceTypeMismatchSoloError — Validation

ServiceTypeMismatchSoloError

CodeSOLO-4060
CategoryValidation
OwnershipInfrastructure
RetryableNo

Description

Thrown when a Kubernetes service is not the expected network-node service; the message names the service. solo expects a service of a specific kind when resolving node endpoints, so this means the service exists but is of the wrong type — indicating an unexpected cluster state.

Troubleshooting Steps

  1. Check solo logs: tail -n 100 ~/.solo/logs/solo.log
  2. Inspect Kubernetes services: kubectl get svc -n
  3. Verify the network is deployed correctly: solo consensus network deploy