2019-04-29 15:57:24 +00:00
|
|
|
---
|
|
|
|
|
name: Bug report
|
2020-04-27 18:10:14 +00:00
|
|
|
about: Create a bug report for IPFS Cluster.
|
2019-04-29 15:57:24 +00:00
|
|
|
title: ''
|
2020-04-27 17:48:31 +00:00
|
|
|
labels: kind/bug, need/triage
|
2019-04-29 15:57:24 +00:00
|
|
|
assignees: ''
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
<!--
|
|
|
|
|
You are about to open an issue in the ipfs-cluster repository. Please verify that:
|
|
|
|
|
|
2019-04-29 16:00:20 +00:00
|
|
|
* You read the troubleshooting docs (https://cluster.ipfs.io/documentation/troubleshooting/)
|
2019-04-29 15:57:24 +00:00
|
|
|
* You searched for similar issues in the repo without luck
|
|
|
|
|
* All peers are configured using the same cluster `secret`
|
|
|
|
|
|
|
|
|
|
Thank you!
|
|
|
|
|
-->
|
|
|
|
|
|
|
|
|
|
**Additional information:**
|
|
|
|
|
- OS: [e.g. Linux]
|
|
|
|
|
- IPFS Cluster version: [e.g. 0.10.1, master]
|
|
|
|
|
- Installation method: [e.g. built from source, dist.ipfs.io, docker]
|
|
|
|
|
|
|
|
|
|
**Describe the bug:**
|
|
|
|
|
|
|
|
|
|
A clear and concise description of what the bug is and how the behavior was different from expected.
|
