Automation Suite on EKS/AKS installation guide

Last updated Oct 3, 2025

Other troubleshooting

If you encounter general issues while configuring or using Automation Suite, refer to the following:

Velero backup fails with FailedValidation error

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 foundPhase: 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 velero
```
Confirm 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 spec section, 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 --all

Alternatively, 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 velero

Confirm that the PHASE is Available and the DEFAULT column shows Yes.

Accessing FQDN returns RBAC: access denied error

Description

Accessing an FQDN may return the following error:

RBAC: access deniedRBAC: access denied

This issue occurs because the FQDN and its relevant URL access are routed via Istio. Istio relies on a WASM plugin to route the request to the appropriate destination pod.

If the WASM plugin image is missing in the registry, internal or external, Istio blocks the URL access and returns a RBAC: access denied error.

Solution

To address this issue, you must ensure that the registry is hydrated and the WASM plugin image exists in registry.

To check the WASM plugin image, run teh folowing command:

kubectl get wasmplugin -A -o yaml | grep urlkubectl get wasmplugin -A -o yaml | grep url

The output will be similar to the one from the following example:

url: oci://testing.azurecr.io/istio-wasm-plugin:2024.10.3url: oci://testing.azurecr.io/istio-wasm-plugin:2024.10.3

In the example above, the WASM plugin image is istio-wasm-plugin:2024.10.3. You must check if this image is present in your registry or not.

On this page

Velero backup fails with FailedValidation error
Accessing FQDN returns RBAC: access denied error
Description
Solution

Was this page helpful?

PREVIOUSUpgrade fails due to overridden Insights PVC sizes

NEXTThe backup setup does not work due to a failure to connect to Azure Government

Support and Services

Get The Help You Need

UiPath Academy

Learning RPA - Automation Courses

UiPath Forum

UiPath Community Forum

Trust and Security

Cookies Policy