- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the service mesh
- Installing and configuring the GitOps tool
- Installing the External Secrets Operator in Kubernetes
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library installation
- AI Trust Layer
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Velero backup fails with FailedValidation error
- External Secrets troubleshooting
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- TLS certificate validation errors
- Fluentd does not export logs in IPv6 environments
- Studio Desktop cannot load Integration Service connectors and activities
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
- Configuring resource requests and limits for uipathctl-created workloads
Velero backup fails with FailedValidation error
Solutions for Velero backup FailedValidation errors in Automation Suite on EKS/AKS.
When attempting to run a scheduled backup in Automation Suite on EKS/AKS, Velero may return the following error:
Phase: FailedValidation
Validation errors: an existing backup storage location was not specified at backup creation time and the server default default does not exist.
Error: BackupStorageLocation.velero.io "default" not found
Phase: FailedValidation
Validation errors: an existing backup storage location was not specified at backup creation time and the server default default does not exist.
Error: BackupStorageLocation.velero.io "default" not found
This occurs due to the default-bs1 BackupStorageLocation not being marked as default in the Velero configuration.
To address the issue, take the following steps:
-
Verify the backup storage locations configured for Velero:
kubectl get backupstoragelocations -n velerokubectl get backupstoragelocations -n veleroConfirm whether the DEFAULT column is empty.
-
Edit the backup storage location to set the default value:
kubectl edit backupstoragelocation default-bs1 -n velerokubectl edit backupstoragelocation default-bs1 -n velero -
Under the
specsection, add the following line:default: truedefault: true -
Save the changes.
-
Restart the Velero pods to apply the configuration:
kubectl delete pod -n velero --allkubectl delete pod -n velero --allAlternatively, perform a rolling restart:
kubectl -n velero rollout restart deploy/velerokubectl -n velero rollout restart deploy/velero -
Verify the fix:
kubectl get backupstoragelocations -n velerokubectl get backupstoragelocations -n veleroConfirm that the
PHASEis Available and the DEFAULT column showsYes.