Closed mscott83 closed 1 year ago
Can you copy the output of "describe" of the "default" BSL? Usually, there should be a message stating the reason for any issues (such as authentication problem).
BTW, the key should be "aws_access_key_id". In your snippet above, it is "aws_access_key". May be that is the issue here.
@draghuram you win the prize, I should have used "aws_access_key_id". When I corrected that and re-installed, it worked fine.
Amazing that you can spend hours troubleshooting something and fail to spot the most basic config error. Thank you so much for your help!
Glad to be of help. And it is true that fresh eyes can see what you miss after staring at it for hours!
What steps did you take and what happened: Brand new install of Velero using the following installation command:
velero install --provider aws --plugins velero/velero-plugin-for-aws:v1.7.0 --bucket my-velero-backups --backup-location-config region=eu-west-2 --snapshot-location-config region=eu-west-2 --secret-file ./credentials-velero
credentials-velero contains the following:
After the installation completes, the "default" BackupStorageLocation exists but shows as "Unavailable". I've checked the the credentials exist in the "cloud-credentials" secret, and they are valid. I don't know how to troubleshoot this further.
What did you expect to happen: Everything installs and works normally
The following information will help us better understand what's going on:
kubectl logs deployment/velero -n velero
Anything else you would like to add:
Environment:
velero version
): v1.11.0velero client config get features
): (features:kubectl version
): v1.26.5/etc/os-release
): Fedora CoreOSVote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.