Bug #582
closed
Foreman should not fail if libvirt ruby binding are not installed
Added by Ohad Levy almost 14 years ago.
Updated almost 14 years ago.
Description
If the binding are missing, we should simply not allow to manage libvirt
Files
just for general info, the ruby-libvirt package is required (and a package is avail for most platforms -- see more details here Virtual Machine Provisioning
if the error you get is that virt is missing and you are using source, you should follow the Upgrade_instructions
Since I currently don't use the virtual machine provisioning features of Foreman and don't want to depend on virt and libvirt, I tried to decouple Foreman from these dependencies.
The attached patch is working on my development setup but it probably needs some more testing.
This patch did not work for me exactly. I had to comment out the config.gem 'virt' and 'libvirt' in config/environment.rb. I also had to comment out the 'require libvirt' in vendor/plugins/virt/lib/virt/connection.rb.
- Status changed from New to Ready For Testing
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by