Velero issues - Revision history

Busk at 15:18, 8 November 2024

2024-11-08T15:18:30Z

Busk at 20:04, 20 June 2023

2023-06-20T20:04:46Z

Busk: Created page with " https://gist.github.com/alexcpn/4de6a5ae242de9de6cbfdb3ffea40977 ``` "Error getting volume snapshotter for volume snapshot location" missing region ```"

2023-06-17T14:21:13Z

Created page with " https://gist.github.com/alexcpn/4de6a5ae242de9de6cbfdb3ffea40977 ``` "Error getting volume snapshotter for volume snapshot location" missing region ```"

New page

https://gist.github.com/alexcpn/4de6a5ae242de9de6cbfdb3ffea40977
```
"Error getting volume snapshotter for volume snapshot location" missing region
```

← Older revision		Revision as of 15:18, 8 November 2024
Line 9:		Line 9:
	"Error getting volume snapshotter for volume snapshot location" missing region		"Error getting volume snapshotter for volume snapshot location" missing region
	```		```
		+
		+	# Phase Unavailable
		+
		+	velero backup-location get -o yaml
		+
		+	The Unavailable status for the backup location in Velero can occur due to several reasons. Here are some common causes to investigate:
		+
		+	Network Connectivity Issues: Velero may be unable to reach the Azure storage account due to network issues, firewall rules, or DNS resolution problems.
		+
		+	Invalid Credentials: The credentials provided for Azure storage access may be incorrect or have expired. Verify the AZURE_CREDENTIALS_FILE (or equivalent) and ensure that the credentials have permissions to access the specified storage container.
		+
		+	Storage Account or Container Misconfiguration: Ensure that the specified storage account and container (velero in this case) exist and are accessible. The container should also have the appropriate access permissions set (e.g., public access level or specific account permissions).
		+
		+	Permissions on the Bucket: Confirm that the service principal or managed identity used by Velero has at least Blob Contributor permissions on the specified container.
		+
		+	Time Sync Issues: If the time on the Velero pod or the Kubernetes node is significantly out of sync, authentication might fail due to token expiry issues. Verify that time synchronization is working properly.
		+
		+	Invalid Region Configuration: Ensure that the region of the Azure storage matches the region configuration in Velero, as mismatched regions can cause access issues.
		+
		+	To troubleshoot, try:
		+
		+	Checking the Velero logs (kubectl logs deploy/velero -n velero).
		+	Running velero backup-location validate default to see if there are specific error messages.
		+	Verifying the connectivity to Azure storage manually using Azure CLI.

← Older revision		Revision as of 20:04, 20 June 2023
Line 1:		Line 1:
		+	# API Throttling
		+	https://github.com/vmware-tanzu/velero/issues/3191
		+	```
		+	Waited for 1.047455292s due to client-side throttling, not priority and fairness, request: GET:https://10.0.0.1:443/apis/rbac.authorization.k8s.io/v1?timeout=32s
		+	```

	https://gist.github.com/alexcpn/4de6a5ae242de9de6cbfdb3ffea40977		https://gist.github.com/alexcpn/4de6a5ae242de9de6cbfdb3ffea40977