mirrors/velero
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/velero.git synced 2026-01-03 11:45:20 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Add Kopia repository ownership issue in troubleshooting.md (#9039)

Browse Source 
Signed-off-by: Xun Jiang <xun.jiang@broadcom.com>
This commit is contained in:
Xun Jiang/Bruce Jiang
2025-06-27 08:50:50 +08:00
committed by GitHub
parent 5ebb055c57
commit d54d88dec9
1 changed files with 14 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
site/content/docs/main/troubleshooting.md
View File

@@ -222,6 +222,20 @@ Follow the below troubleshooting steps to confirm that Velero is using the corre
Ensure that the key exists within the secret's data by checking the output from `kubectl -n velero describe secret $BSL_SECRET` or `kubectl -n velero describe secret $VSL_SECRET`.
If it does not exist, follow the instructions for [editing a Kubernetes secret][12] to add the base64 encoded credentials data.
## Kopia repository files' ownership mismatch
Velero sets the files' ownership created in the Kopia repository to `default@default`.
If users need to use Kopia CLI to connect to the Velero created Kopia repositories, please use the following CLI as an example to avoid overwriting the ownership by accident.
``` bash
kopia repository connect <type> <--read-only> --bucket= --override-username=default --override-hostname=default
```
If the ownership conflict error(`maintenance must be run by designated user`) already happens,
Velero doesn't handle the conflict by design.
To resolve it, please use Kopia maintenance CLI to set the ownership correctly, e.g. `kopia maintenance set --owner=default@default`.
Please refer to [Issue 9007](https://github.com/vmware-tanzu/velero/issues/9007) for more information.
[1]: debugging-restores.md
[2]: debugging-install.md