-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This plugin breaks the vagrant-libvirt hostnames #107
Comments
Tracked in vagrant-libvirt as: vagrant-libvirt/vagrant-libvirt#215 |
Not vagrant-hostmanager's fault. I incorrectly thought it was a change this plugin did, when really it was vagrant-libvirt that changed without me realizing. Sorry for the noise. |
No problem. I was just starting to look at it. Good timing. 😃 |
Hi James. Thanks for contributing. |
On Sat, Jul 26, 2014 at 9:34 AM, Paulo Bittencourt <[email protected]
Sounds good. I might have one subsequent change to one of those patches to |
I just tried this out with vagrant-libvirt. It mostly seems to work great. The biggest issue:
When using this, it changes the host name (as seen from the vagrant-libvirt perspective) from hostname to
Example:
hosts_1406096813_626657195ee18d615f84
I'm not entirely sure who's fault this is, if it's vagrant-libvirt or this plugin, but whatever the case, if someone can help me understand why / how this happens, and point me in the right direction, then I'll patch it.
Thanks,
James
The text was updated successfully, but these errors were encountered: