Repository metrics
- Stars
- (10,111 stars)
- PR merge metrics
- (PR metrics pending)
Description
What steps did you take and what happened: Backups and maintenance runs smoothly over a week but suddenly deletion process fails after a while randomly. From the Velero logs I can see that the AWS session token has expired. See log line below.
What did you expect to happen: If the token has expired I expect Velero/Kopia to get a new token and retry. The backups deletion become stuck until Velero deployment is restarted. I expect not having to restart the pod.
The following information will help us better understand what's going on:
Backup isn't the problem it's the delete maintenance, here is the log of the error:
time="2026-06-25T10:32:32Z" level=warning msg="failed to open repository: cannot open storage: error retrieving storage config from bucket \"<redacted>\": The provided token has expired" logModule=kopia/kopia/repo logSource="pkg/kopia/kopia_log.go:110" sublevel=error
Anything else you would like to add: Mitigation is restarting the pod, eventually we would prefer not to do it.
Environment:
- Velero version (use
velero version):
Client:
Version: v1.18.1
Git commit: -
Server:
Version: v1.18.1
- Velero features (use
velero client config get features): features: NOT SET - Kubernetes version (use
kubectl version):
Client Version: v1.36.1
Kustomize Version: v5.8.1
Server Version: v1.35.5-eks-0247562
- Kubernetes installer & version: eks via terraform
- Cloud provider or hardware configuration: aws
- OS (e.g. from
/etc/os-release): bottlerocket on k8s
Vote 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.
- :+1: for "I would like to see this bug fixed as soon as possible"
- :-1: for "There are more important bugs to focus on right now"