Project

General

Profile

Bug #582

Foreman should not fail if libvirt ruby binding are not installed

Added by Ohad Levy over 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
VM management
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

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 0001-Fixes-bug-582-make-dependency-on-libvirt-optional-th.patch 4.45 KB Proposed patch to make dependency on libvirt optional Jochen Schalanda, 02/07/2011 09:50 AM

Associated revisions

Revision ba5b7e74 (diff)
Added by Ohad Levy about 8 years ago

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

History

#1 Updated by Ohad Levy over 8 years 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

#2 Updated by Jochen Schalanda over 8 years 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.

#3 Updated by Chad Huneycutt over 8 years 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.

#4 Updated by Ohad Levy about 8 years ago

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

#5 Updated by Ohad Levy about 8 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF