2018-04-25 16:08:54 +00:00
# Debugging Installation Issues
## General
### `invalid configuration: no configuration has been provided`
2019-05-28 16:42:27 +00:00
This typically means that no `kubeconfig` file can be found for the Velero client to use. Velero looks for a kubeconfig in the
2018-04-25 16:08:54 +00:00
following locations:
* the path specified by the `--kubeconfig` flag, if any
* the path specified by the `$KUBECONFIG` environment variable, if any
* `~/.kube/config`
### Backups or restores stuck in `New` phase
2019-01-25 03:33:07 +00:00
This means that the Velero controllers are not processing the backups/restores, which usually happens because the Velero server is not running. Check the pod description and logs for errors:
2018-04-25 16:08:54 +00:00
```
2019-01-25 03:33:07 +00:00
kubectl -n velero describe pods
kubectl -n velero logs deployment/velero
2018-04-25 16:08:54 +00:00
```
## AWS
### `NoCredentialProviders: no valid providers in chain`
2019-01-28 11:34:53 +00:00
#### Using credentials
2019-05-28 16:42:27 +00:00
This means that the secret containing the AWS IAM user credentials for Velero has not been created/mounted properly
2019-01-25 03:33:07 +00:00
into the Velero server pod. Ensure the following:
2019-05-28 16:42:27 +00:00
2019-01-25 03:33:07 +00:00
* The `cloud-credentials` secret exists in the Velero server's namespace
* The `cloud-credentials` secret has a single key, `cloud` , whose value is the contents of the `credentials-velero` file
* The `credentials-velero` file is formatted properly and has the correct values:
2019-05-28 16:42:27 +00:00
2018-04-25 16:08:54 +00:00
```
[default]
aws_access_key_id=< your AWS access key ID >
aws_secret_access_key=< your AWS secret access key >
```
2019-05-28 16:42:27 +00:00
2019-01-25 03:33:07 +00:00
* The `cloud-credentials` secret is defined as a volume for the Velero deployment
* The `cloud-credentials` secret is being mounted into the Velero server pod at `/credentials`
2018-04-25 16:08:54 +00:00
2019-01-28 11:34:53 +00:00
#### Using kube2iam
2019-04-29 19:33:54 +00:00
This means that Velero can't read the content of the S3 bucket. Ensure the following:
2019-05-28 16:42:27 +00:00
2019-04-29 19:33:54 +00:00
* There is a Trust Policy document allowing the role used by kube2iam to assume Velero's role, as stated in the AWS config documentation.
* The new Velero role has all the permissions listed in the documentation regarding S3.
2019-01-28 11:34:53 +00:00
2018-04-25 16:08:54 +00:00
## Azure
### `Failed to refresh the Token` or `adal: Refresh request failed`
2019-05-28 16:42:27 +00:00
This means that the secrets containing the Azure service principal credentials for Velero has not been created/mounted
2019-01-25 03:33:07 +00:00
properly into the Velero server pod. Ensure the following:
2019-05-28 16:42:27 +00:00
2019-01-25 03:33:07 +00:00
* The `cloud-credentials` secret exists in the Velero server's namespace
2018-08-27 19:21:50 +00:00
* The `cloud-credentials` secret has all of the expected keys and each one has the correct value (see [setup instructions ](0 ))
2019-01-25 03:33:07 +00:00
* The `cloud-credentials` secret is defined as a volume for the Velero deployment
* The `cloud-credentials` secret is being mounted into the Velero server pod at `/credentials`
2018-04-25 16:08:54 +00:00
## GCE/GKE
### `open credentials/cloud: no such file or directory`
2019-05-28 16:42:27 +00:00
This means that the secret containing the GCE service account credentials for Velero has not been created/mounted properly
2019-01-25 03:33:07 +00:00
into the Velero server pod. Ensure the following:
2019-05-28 16:42:27 +00:00
2019-01-25 03:33:07 +00:00
* The `cloud-credentials` secret exists in the Velero server's namespace
* The `cloud-credentials` secret has a single key, `cloud` , whose value is the contents of the `credentials-velero` file
* The `cloud-credentials` secret is defined as a volume for the Velero deployment
* The `cloud-credentials` secret is being mounted into the Velero server pod at `/credentials`
2018-04-25 16:08:54 +00:00
2019-01-28 11:34:53 +00:00
[0]: azure-config#credentials-and-configuration