From 37ef4979a46f4b6fb51afb8af1c8eccffecf441d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=A9bastien=20Han?= Date: Thu, 11 Jul 2019 14:30:25 +0200 Subject: [PATCH] issue: update template MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit We need more information when opening bugs such as: * logs from pod and operator * cluster CR Signed-off-by: Sébastien Han --- .github/ISSUE_TEMPLATE/bug_report.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 027d8a65c..96a044be8 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -18,11 +18,22 @@ labels: bug **How to reproduce it (minimal and precise):** +**File(s) to submit**: + +* Cluster CR (custom ressource), typically called `cluster.yaml`, if necessary +* Operator's logs, if necessary +* Crashing pod(s) logs, if necessary + + To get logs, use `kubectl -n logs ` +When pasting logs, always surround them with backticks or use the `insert code` button from the Github UI. +Read [Github documentation if you need help](https://help.github.com/en/articles/creating-and-highlighting-code-blocks). + **Environment**: * OS (e.g. from /etc/os-release): * Kernel (e.g. `uname -a`): * Cloud provider or hardware configuration: * Rook version (use `rook version` inside of a Rook Pod): +* Storage backend version (e.g. for ceph do `ceph -v`): * Kubernetes version (use `kubectl version`): * Kubernetes cluster type (e.g. Tectonic, GKE, OpenShift): * Storage backend status (e.g. for Ceph use `ceph health` in the [Rook Ceph toolbox](https://rook.io/docs/rook/master/ceph-toolbox.html)):