vmware-tanzu
/
velero
mirror of https://github.com/vmware-tanzu/velero.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #823 from nrb/sig-error-docs 

Document SignatureDoesNotMatch error and triaging
pull/829/head
Steve Kriss 2018-09-07 09:51:12 -06:00 committed by GitHub
parent 44a75cee7b 779cb42854
commit 086d0667de
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 23 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/faq.md
View File

@ -35,9 +35,5 @@ Related to this, if you need to restore a backup from cluster A into cluster B,
mode in cluster B's Ark instance while it's configured to use cluster A's bucket. This will ensure no
new backups are created, and no existing backups are deleted or overwritten.
## I receive 'custom resource not found' errors when starting up the Ark server
Ark's server will not start if the required Custom Resource Definitions are not found in Kubernetes. Apply
the `examples/common/00-prereqs.yaml` file to create these defintions, then restart Ark.
[1]: config-definition.md#main-config-parameters

26
docs/troubleshooting.md
View File

@ -33,11 +33,31 @@ kubectl edit deployment/ark -n heptio-ark
```
* [Debug installation/setup issues][2]
## [Debug installation/setup issues][2]
## [Debug restores][1]
## Miscellaneous issues
### Ark reports `custom resource not found` errors when starting up.
Ark's server will not start if the required Custom Resource Definitions are not found in Kubernetes. Apply
the `examples/common/00-prereqs.yaml` file to create these defintions, then restart Ark.
### `ark backup logs` returns a `SignatureDoesNotMatch` error
Downloading artifacts from object storage utilizes temporary, signed URLs. In the case of S3-compatible
providers, such as Ceph, there may be differences between their implementation and the official S3
API that cause errors.
Here are some things to verify if you receive `SignatureDoesNotMatch` errors:
* Make sure your S3-compatible layer is using [signature version 4][5] (such as Ceph RADOS v12.2.7)
* For Ceph, try using a native Ceph account for credentials instead of external providers such as OpenStack Keystone
* [Debug restores][1]
[1]: debugging-restores.md
[2]: debugging-install.md
[4]: https://github.com/heptio/ark/issues
[25]: https://kubernetes.slack.com/messages/ark-dr
[5]: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html
[25]: https://kubernetes.slack.com/messages/ark-dr