2018-05-10 19:15:21 +00:00
---
name: Bug Report
about: You're experiencing an issue with Consul that is different than the documented behavior.
---
2018-08-28 16:07:28 +00:00
When filing a bug, please include the following headings if possible. Any example text in this template can be deleted.
2018-05-10 19:15:21 +00:00
#### Overview of the Issue
A paragraph or two about the issue you're experiencing.
#### Reproduction Steps
Steps to reproduce this issue, eg:
1. Create a cluster with n client nodes n and n server nodes
1. Run `curl ...`
1. View error
### Consul info for both Client and Server
2018-05-10 19:55:26 +00:00
< details >
< summary > Client info< / summary >
2018-05-11 00:29:50 +00:00
2018-05-10 19:15:21 +00:00
```
2018-05-10 19:55:26 +00:00
output from client 'consul info' command here
2018-05-10 19:15:21 +00:00
```
2018-05-11 00:29:50 +00:00
< / details >
2018-05-10 19:15:21 +00:00
2018-05-10 19:55:26 +00:00
< details >
2018-05-11 00:27:12 +00:00
< summary > Server info< / summary >
2018-05-11 00:29:50 +00:00
2018-05-10 19:15:21 +00:00
```
2018-05-10 19:55:26 +00:00
output from server 'consul info' command here
2018-05-10 19:15:21 +00:00
```
2018-05-11 00:29:50 +00:00
< / details >
2018-05-10 19:15:21 +00:00
### Operating system and Environment details
2018-08-28 16:07:28 +00:00
OS, Architecture, and any other information you can provide about the environment.
2018-05-10 19:15:21 +00:00
### Log Fragments
2018-08-28 16:07:28 +00:00
Include appropriate Client or Server log fragments. If the log is longer than a few dozen lines, please include the URL to the [gist ](https://gist.github.com/ ) of the log instead of posting it in the issue. Use `-log-level=TRACE` on the client and server to capture the maximum log detail.