Bug #582

Foreman should not fail if libvirt ruby binding are not installed

Added by Ohad Levy over 1 year ago. Updated about 1 year ago.

Status:Closed Start:01/14/2011
Priority:Normal Due date:
Assigned to:Ohad Levy % Done:

100%
Category:VM management
Target version:0.2
Backlog:No Difficulity:
Votes: 0

Description

If the binding are missing, we should simply not allow to manage libvirt

0001-Fixes-bug-582-make-dependency-on-libvirt-optional-th.patch - Proposed patch to make dependency on libvirt optional (4.4 KB) Jochen Schalanda, 02/07/2011 09:50 am

Associated revisions

Revision ba5b7e74e0b0f8b7efcb8804f77c810031a6aeba
Added by Ohad Levy about 1 year ago

fixes #582 - Foreman should not fail if libvirt ruby binding are not installed

History

Updated by Ohad Levy over 1 year ago

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

Updated by Jochen Schalanda over 1 year ago

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.

Updated by Chad Huneycutt over 1 year ago

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.

Updated by Ohad Levy about 1 year ago

  • Status changed from New to Ready For Testing
  • % Done changed from 0 to 100

Updated by Ohad Levy about 1 year ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF