mirror of
https://github.com/vagrant-libvirt/vagrant-libvirt.git
synced 2025-02-25 18:55:27 -06:00
d3daf962e3
Github supports attaching files, therefore switch to suggesting users attach the debug output instead of inserting to make it easier to quickly read over the issue.
38 lines
1.2 KiB
Markdown
38 lines
1.2 KiB
Markdown
<!--
|
|
Thank you for reporting issues to vagrant-libvirt.
|
|
|
|
To make it possible for us to help you quickly, we kindly request that you use the template below to report issues. If the issue you are reporting does not fit the template (a feature request for example) please feel free to adapt it to your needs.
|
|
|
|
Please be aware that we are not actively testing previous versions of both Vagrant and Vagrant-libvirt, so before reporting an issue, please install the latest Vagrant version from Vagrantup.com, run `vagrant plugin update` and reproduce the issue.
|
|
-->
|
|
### Steps to reproduce
|
|
1.
|
|
2.
|
|
3.
|
|
|
|
### Expected behaviour
|
|
Tell us what should happen
|
|
|
|
### Actual behaviour
|
|
Tell us what happens instead
|
|
|
|
### System configuration
|
|
**OS/Distro version:**:
|
|
|
|
**Libvirt version:**
|
|
|
|
**Output of `vagrant version; vagrant plugin list`:**
|
|
|
|
**Attach Output of `VAGRANT_LOG=debug vagrant ... --provider=libvirt >vagrant.log 2>&1`**
|
|
```
|
|
Delete this text and drag and drop the log file for github to attach and add a link here
|
|
```
|
|
|
|
**A Vagrantfile to reproduce the issue:**
|
|
```
|
|
Insert Vagrantfile inside quotes here (remove sensitive data if needed)
|
|
```
|
|
|
|
**Are you using upstream vagrant package or your distros package?**
|
|
Upstream / Distro
|