mirror of
https://github.com/davestephens/ansible-nas
synced 2024-12-27 03:53:06 +00:00
34 lines
1.4 KiB
Markdown
34 lines
1.4 KiB
Markdown
For :bug: bug reports, please fill out the information below plus any additional relevant information. For feature requests, feel free to clear the form.
|
|
|
|
If you're reporting an issue with execution of the Ansible-NAS playbook, please run the playbook with `-vvv`, and ideally isolate the problematic part with `--tags <ansible tag>` where possible.
|
|
|
|
**Short problem description**
|
|
|
|
Enter a couple of lines about the issue.
|
|
|
|
**Environment**
|
|
- Ansible-NAS revision (`git rev-parse --short HEAD`):
|
|
- Ansible version (paste the entire output of `ansible --version` on the machine you run the playbook from):
|
|
- Ansible-NAS operating system (`cat /etc/lsb-release` on the Ansible-NAS box) - _If this is anything other than Ubuntu 18.04 help will be limited_:
|
|
- Ansible-NAS kernel (`cat /etc/lsb-release` on the Ansible-NAS box):
|
|
- Ansible-NAS Python version (`python --version` on the Ansible-NAS box):
|
|
- Ansible-NAS Docker version (`docker --version` on the Ansible-NAS box):
|
|
- Latest Docker logs (`journalctl -u docker.service` on the Ansible-NAS box):
|
|
- Are you running the playbook from a remote box or the Ansible-NAS box itself?
|
|
- Vagrant version, if testing (`vagrant --version`)
|
|
|
|
**Expected behavior**
|
|
|
|
What should happen?
|
|
|
|
**Actual behavior**
|
|
|
|
What actually happens?
|
|
|
|
**Steps to reproduce**
|
|
|
|
What does someone need to do to reproduce this?
|
|
|
|
**Playbook Output**
|
|
|
|
Paste the output of the playbook at the problematic point.
|