Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intermittent Backup Failures in Velero with "failed to refresh cached credentials" Error #8524

Open
halaMayday opened this issue Dec 18, 2024 · 1 comment
Assignees
Labels
Area/Cloud/AWS Needs info Waiting for information

Comments

@halaMayday
Copy link

halaMayday commented Dec 18, 2024

What steps did you take and what happened:

We are using Velero with the velero-plugin-for-aws to perform daily full backups. Every day, we execute backups for over 300 applications, with approximately 10 backups for different applications being executed every 5 minutes. However, we consistently experience occasional backup failures. The error message encountered during these failures is as follows:

time="2024-12-18T06:28:57+08:00" level=error msg="Error getting backup store for this location" backupLocation=xxxxxx controller=backup-sync error="rpc error: code = Unknown desc = failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, request canceled, context deadline exceeded" error.file="velero-plugin-for-aws/velero-plugin-for-aws/object_store.go:150" error.function="main.(*ObjectStore).Init" logSource="pkg/controller/backup_sync_controller.go:111"

This issue consistently happens every day, affecting a small number of backups.

Environment:

  • Velero version: 1.13.1
  • Velero plugin for AWS version: 1.9.1
@kaovilai
Copy link
Member

kaovilai commented Dec 19, 2024

Set the AWS env vars and then trick it into using an empty profile, eg:

terraformer import aws -r s3 --profile ""

Found this note here. Can you try setting BSL profile to empty?

@reasonerjt reasonerjt added Area/Cloud/AWS Needs info Waiting for information labels Dec 20, 2024
@reasonerjt reasonerjt self-assigned this Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area/Cloud/AWS Needs info Waiting for information
Projects
None yet
Development

No branches or pull requests

3 participants