SOLO-2025

BackupImportFailedSoloError — Deployment

BackupImportFailedSoloError

CodeSOLO-2025
CategoryDeployment
OwnershipInfrastructure
RetryableNo

Description

Thrown during solo config ops restore-config when a particular resource cannot be imported from a backup; the message names the resourceType and wraps the underlying failure in cause. Restore reads each resource from the backup archive and applies it to the cluster, so this is raised when reading the archive entry or applying it fails — for example the backup archive is incomplete or corrupt, the resource is invalid, or the Kubernetes API is unreachable or rejected it.

Troubleshooting Steps

  1. Check solo logs: tail -n 100 ~/.solo/logs/solo.log
  2. Verify Kubernetes connectivity: kubectl get pods -A
  3. Verify the backup archive is complete and valid
  4. Run restore: solo config ops restore-config