Bug #2002

Problem editing Libvirt Host in Foreman

Added by Greg Sutcliffe over 9 years ago. Updated about 9 years ago.

VM management
Target version:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:


This is on my bleeding edge Foreman (ruby 1.9, puppet 3, psql 9.2)

I can create and destroy Libvirt Hosts in Foreman fine, but if I try to edit one, I get this error/trace:

"undefined method `id' for #<Fog::Compute::Libvirt::Nic:0xda7a000>" from app/views/compute_resources_vms/form/_libvirt.html.erb:11

Related issues

Related to Foreman - Bug #2586: Upgrade fog when releasedClosed2013-05-30
Has duplicate Foreman - Bug #2024: (Fog / Libvirt / Rub1.9) cannot edit a Libvirt host Duplicate2012-12-09
Has duplicate Smart Proxy - Bug #2456: Error while testing compute resourcesClosed2013-05-05

Associated revisions

Revision b2c8312c (diff)
Added by Marek Hulán about 9 years ago

Refs #2002 - Fog quick hack

Revision d37be454 (diff)
Added by Marek Hulán about 9 years ago

Refs #2002 - Fog quick hack
(cherry picked from commit b2c8312c6919423a7d77c36468fc8d62dbe874cc)


#1 Updated by Ohad Levy over 9 years ago

can you confirm this happens on ruby 1.9 only?

#2 Updated by Marek Hulán over 9 years ago

  • Status changed from New to Assigned
  • Assignee set to Marek Hulán

I can confirm. In ruby 1.8 every object has a method id that was replaced by object_id in ruby 1.9. The proper fix is in unreleased fog master branch (see We can either wait for a new release or make some monkey patch. However they claim to release soon.

#3 Updated by Greg Sutcliffe over 9 years ago

I don't want to put bundler git gems back in the packaging, it makes a mess :). Let's hope they release a new version.

#4 Updated by Dominic Cleal about 9 years ago

  • Target version set to 1.2.0

I think this is important to fix for 1.2, as we're moving to Ruby 1.9 on the RPMs. I don't think the fix is in the 1.11.1 release, so can we monkey patch?

#5 Updated by Marek Hulán about 9 years ago

  • Status changed from Assigned to Ready For Testing

Before we close this one, we should create a new issue to remove this quick fix in future.

#6 Updated by Ohad Levy about 9 years ago

  • Status changed from Ready For Testing to Resolved

Also available in: Atom PDF