Currently any attempt to use vagrant-libvirt with fog-libvirt newer than 0.0.3 with the current release of ruby-libvirt will result in the following error:Any update on this?A number of months ago it was requested whether a new ruby-libvirt release could be made to include some new functionality that fog-libvirt wished to make use of, see https://www.redhat.com/archives/libvir-list/2016- .March/msg00241.html
/home/baileybd/.vagrant.d/gems/gems/fog-libvirt-0.0.4/ lib/fog/libvirt/requests/ compute/dhcp_leases.rb:8:in `dhcp_leases': NULL pointer given (ArgumentError)
from /home/baileybd/.vagrant.d/gems/gems/fog-libvirt-0.0.4/ lib/fog/libvirt/requests/ compute/dhcp_leases.rb:8:in `dhcp_leases'
from /home/baileybd/.vagrant.d/gems/gems/fog-libvirt-0.0.4/ lib/fog/libvirt/models/ compute/network.rb:20:in `dhcp_leases'
from /home/baileybd/.vagrant.d/gems/gems/fog-libvirt-0.0.4/ lib/fog/libvirt/models/ compute/server.rb:272:in `block in addresses'
from /home/baileybd/.vagrant.d/gems/gems/fog-core-1.42.0/lib/ fog/core/collection.rb:19:in `each'
from /home/baileybd/.vagrant.d/gems/gems/fog-core-1.42.0/lib/ fog/core/collection.rb:19:in `each'
from /home/baileybd/.vagrant.d/gems/gems/fog-libvirt-0.0.4/ lib/fog/libvirt/models/ compute/server.rb:270:in `addresses'
from /home/baileybd/.vagrant.d/gems/gems/vagrant-libvirt-0.0. 32.hp.2/lib/vagrant-libvirt/ action/wait_till_up.rb:44:in `block (3 levels) in call'
from /home/baileybd/.vagrant.d/gems/gems/fog-core-1.42.0/lib/ fog/core/model.rb:72:in `instance_eval'
from /home/baileybd/.vagrant.d/gems/gems/fog-core-1.42.0/lib/ fog/core/model.rb:72:in `block in wait_for'
from /home/baileybd/.vagrant.d/gems/gems/fog-core-1.42.0/lib/ fog/core/wait_for.rb:7:in `block in wait_for'
from /home/baileybd/.vagrant.d/gems/gems/fog-core-1.42.0/lib/ fog/core/wait_for.rb:6:in `loop'
from /home/baileybd/.vagrant.d/gems/gems/fog-core-1.42.0/lib/ fog/core/wait_for.rb:6:in `wait_for'
from /home/baileybd/.vagrant.d/gems/gems/fog-core-1.42.0/lib/ fog/core/model.rb:69:in `wait_for'
It appears the patch required to resolve was landed in January:
http://libvirt.org/git/?p=ruby-libvirt.git;a=commit;h= c2d4192ebf28b8030b753b715a72f0 cdf725d313
--Darragh Bailey
"Nothing is foolproof to a sufficiently talented fool"
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list