mirror of
https://github.com/netbox-community/netbox.git
synced 2024-05-10 07:54:54 +00:00
43 lines
1.3 KiB
Markdown
43 lines
1.3 KiB
Markdown
---
|
|
name: 🐛 Bug Report
|
|
about: Report a reproducible bug in the current release of NetBox
|
|
|
|
---
|
|
|
|
<!--
|
|
NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED.
|
|
|
|
This form is only for reproducible bugs. If you need assistance with
|
|
NetBox installation, or if you have a general question, DO NOT open an
|
|
issue. Instead, post to our mailing list:
|
|
|
|
https://groups.google.com/forum/#!forum/netbox-discuss
|
|
|
|
Please describe the environment in which you are running NetBox. Be sure
|
|
that you are running an unmodified instance of the latest stable release
|
|
before submitting a bug report, and that any plugins have been disabled.
|
|
-->
|
|
### Environment
|
|
* Python version:
|
|
* NetBox version:
|
|
|
|
<!--
|
|
Describe in detail the exact steps that someone else can take to reproduce
|
|
this bug using the current stable release of NetBox. Begin with the
|
|
creation of any necessary database objects and call out every operation
|
|
being performed explicitly. If reporting a bug in the REST API, be sure to
|
|
reconstruct the raw HTTP request(s) being made: Don't rely on a client
|
|
library such as pynetbox.
|
|
-->
|
|
### Steps to Reproduce
|
|
1.
|
|
2.
|
|
3.
|
|
|
|
<!-- What did you expect to happen? -->
|
|
### Expected Behavior
|
|
|
|
|
|
<!-- What happened instead? -->
|
|
### Observed Behavior
|