|
| 1 | +--- |
| 2 | +name: Mitogen 0.2.x bug report |
| 3 | +about: Report a bug in Mitogen 0.2.x (for Ansible 2.5, 2.6, 2.7, 2.8, or 2.9) |
| 4 | +title: '' |
| 5 | +labels: affects-0.2, bug |
| 6 | +assignees: '' |
| 7 | + |
| 8 | +--- |
| 9 | + |
| 10 | +Please drag-drop large logs as text file attachments. |
| 11 | + |
| 12 | +Feel free to write an issue in your preferred format, however if in doubt, use |
| 13 | +the following checklist as a guide for what to include. |
| 14 | + |
| 15 | +* Which version of Ansible are you running? |
| 16 | +* Is your version of Ansible patched in any way? |
| 17 | +* Are you running with any custom modules, or `module_utils` loaded? |
| 18 | + |
| 19 | +* Have you tried the latest master version from Git? |
| 20 | +* Do you have some idea of what the underlying problem may be? |
| 21 | + https://mitogen.networkgenomics.com/ansible_detailed.html#common-problems has |
| 22 | + instructions to help figure out the likely cause and how to gather relevant |
| 23 | + logs. |
| 24 | +* Mention your host and target OS and versions |
| 25 | +* Mention your host and target Python versions |
| 26 | +* If reporting a performance issue, mention the number of targets and a rough |
| 27 | + description of your workload (lots of copies, lots of tiny file edits, etc.) |
| 28 | +* If reporting a crash or hang in Ansible, please rerun with -vvv and include |
| 29 | + 200 lines of output around the point of the error, along with a full copy of |
| 30 | + any traceback or error text in the log. Beware "-vvv" may include secret |
| 31 | + data! Edit as necessary before posting. |
| 32 | +* If reporting any kind of problem with Ansible, please include the Ansible |
| 33 | + version along with output of "ansible-config dump --only-changed". |
0 commit comments