-
Notifications
You must be signed in to change notification settings - Fork 43
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
vagrant up fails with fog-libvirt 0.0.4, works with 0.0.3 #16
Comments
Albert thanks for opening this issue, i think we are first to hit this issue, could you please guide me how to degrade to fog-libvirt 0.0.3 ? will be obliged |
I can confirm I also have the issue for 0.0.4 and moving to 0.0.3 fixes the problem. |
problem solved, it was with newer version of fog-libvirt 0.0.4.......reverting it back to 0.0.3 solved my problem. |
To downgrade the plugin I did (on debian/jessie): /usr/bin/ruby2.1 /usr/lib/ruby/vendor_ruby/vagrant/pre-rubygems.rb plugin install --plugin-version 0.0.3 fog-libvirt It seems that "vagrant plugin install plugin plugin-name" does not support the specification of plugin version, at least in vagrant 1.6.5. |
can confirm on opsensuse Leap, |
@strzibny sure, but I do not know how to bisect vagrant plugins using the source.
but the error seems the the same. Please provide some instruction. Thanks. |
Do we know where is the issue? |
Hey guys, I have confirmed that commit 21d1b71 appears to be causing these problems. I checked out the latest fog-libvirt code. I did a Unfortunately, I don't know why this problem occurs with 21d1b71. I worry that it might be executing some libvirt stuff before the library is fully configured. |
Also, to answer @strzibny 's question, I am testing with
|
You need at least vagrant-libvirt 0.6.0 plus http://libvirt.org/git/?p=ruby-libvirt.git;a=commit;h=c2d4192ebf28b8030b753b715a72f0cdf725d313 . Do you have that commit in your vagrant-libvirt? |
@dcbw , is this problem occurring because we are using |
@sford yes, that is my current theory. ruby-libvirt 0.6.0 is not quite new enough. I will try to request a new upstream release. |
If you're hitting this, do you have a ~/.fog file and if so what's in it? |
Nope, I don't have a |
I can reproduce now, the ~/.fog I was using while developing the original patch was likely covering up the issue for me. |
Hi Folks, I am also hitting this issue. What is the proposed solution for this? |
A quick workaround is to add a ~/.fog file with something like: default: |
@dcbw : Adding However, this |
@dcbw applying #17 does get me further:
I have also applied the the following ruby-libvirt patch with the same error above. |
@dcbw any traction with a new ruby-libvirt release or #17? Some projects (vagrant-libvirt/vagrant-libvirt#569) are pinning fog-libvirt to an older version which makes it harder for them to take advantage of other fog-libvirt improvements (#15). |
@bcambl that error means that the ruby-libvirt patch was not successfully applied, or the rebuilt ruby-libvirt isn't acutally being used. I know, I had the same problem and there was a stale ruby-libvirt in ~/.gems but the patched one was in /usr/share/gems. I had to remove the ~/.gems one to get things working. |
@sford no response in a couple weeks from upstream ruby-libvirt, I'll ping them again. |
@dcbw you are correct, I had something stale. All is well with fog-libvirt 0.0.4 + #17 and the latest ruby-libvirt:
|
Running Fedora 23 (fully updated) with vagrant-libvirt 0.0.32 and fog-libvirt 0.0.4. My vagrant ups are failing with:
I happened to have another vagrant setup with fog-libvirt 0.0.3 and that works fine.
The text was updated successfully, but these errors were encountered: