2018-07-06 12:31:13 +00:00
|
|
|
---
|
|
|
|
name: Bug report
|
|
|
|
about: Tell us about a problem you are experiencing
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
**What steps did you take and what happened:**
|
2018-07-13 21:22:17 +00:00
|
|
|
[A clear and concise description of what the bug is, and what commands you ran.)
|
2018-07-06 12:31:13 +00:00
|
|
|
|
|
|
|
|
|
|
|
**What did you expect to happen:**
|
|
|
|
|
|
|
|
|
2018-07-13 21:22:17 +00:00
|
|
|
**The output of the following commands will help us better understand what's going on**:
|
|
|
|
(Pasting long output into a [GitHub gist](https://gist.github.com) or other pastebin is fine.)
|
|
|
|
|
2019-02-11 19:40:53 +00:00
|
|
|
* `kubectl logs deployment/velero -n velero`
|
|
|
|
* `velero backup describe <backupname>` or `kubectl get backup/<backupname> -n velero -o yaml`
|
|
|
|
* `velero backup logs <backupname>`
|
|
|
|
* `velero restore describe <restorename>` or `kubectl get restore/<restorename> -n velero -o yaml`
|
|
|
|
* `velero restore logs <restorename>`
|
2018-07-13 21:22:17 +00:00
|
|
|
|
|
|
|
|
2018-07-06 12:31:13 +00:00
|
|
|
**Anything else you would like to add:**
|
|
|
|
[Miscellaneous information that will assist in solving the issue.]
|
|
|
|
|
|
|
|
|
|
|
|
**Environment:**
|
|
|
|
|
2019-02-11 19:40:53 +00:00
|
|
|
- Velero version (use `velero version`):
|
2018-07-11 15:00:20 +00:00
|
|
|
- Kubernetes version (use `kubectl version`):
|
2018-07-06 12:31:13 +00:00
|
|
|
- Kubernetes installer & version:
|
|
|
|
- Cloud provider or hardware configuration:
|
|
|
|
- OS (e.g. from `/etc/os-release`):
|