-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Fatal: unable to open config file results in PartiallyFailed Backup #8263
Labels
Comments
Could you try kopia path instead? restic path is being deprecated, so we are not going to work on restic path for troubleshooting or enhancements |
@Lyndon-Li yes I will try that and post my results |
@Lyndon-Li with kopia I am getting a similar error:
Still not sure why the error occurs because the directory |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What steps did you take and what happened:
Unfortunately my backups end up being PartiallyFailed due to the following error:
However, when looking into my bucket with an S3 viewer, there is the repository
/velero/restic/kube-system
and it also contains the config file along with the snapshots etc.I already tried setting various proxy settings, because I run this on-premise and the S3 bucket is an on-premise enterprise object storage, but without success. Since the backup files are uploaded to the S3 buckets just fine, I assume the proxy settings are not relevant. I also tried to install restic on my local machine and tried to verify the repository via
restic -r s3:https://***.net/<bucketname>/velero/restic/kube-system snapshots
which works just fine.Additionally, I am using the velero/velero-plugin-for-aws:v1.9.0 plugin, as it is an S3 compatible storage.
Since I am running everything in our on-premise environment, I don't really want to add the debug information bundle as it might contain sensitive data.
What did you expect to happen:
I expect that the backup executes just fine without being PartiallyFailed.
The following information will help us better understand what's going on:
If you are using velero v1.7.0+:
Please use
velero debug --backup <backupname> --restore <restorename>
to generate the support bundle, and attach to this issue, more options please refer tovelero debug --help
If you are using earlier versions:
Please provide the output of the following commands (Pasting long output into a GitHub gist or other pastebin is fine.)
kubectl logs deployment/velero -n velero
velero backup describe <backupname>
orkubectl get backup/<backupname> -n velero -o yaml
velero backup logs <backupname>
velero restore describe <restorename>
orkubectl get restore/<restorename> -n velero -o yaml
velero restore logs <restorename>
Anything else you would like to add:
Environment:
velero version
): 1.14.1velero client config get features
): n/akubectl version
): 1.31/etc/os-release
): n/aVote 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.
The text was updated successfully, but these errors were encountered: