Bug #1640
Updated by Dominic Cleal over 9 years ago
The following error occurs when trying to view a VM on a Libvirt host that does not have a "default" storage pool: <pre> ArgumentError Initialization parameters must be an attributes hash, got nil app/views/compute_resources/vms/show/_libvirt.html.erb:42:in `_app_views_compute_resources_vms_show__libvirt_html_erb__687762671_70269412929760_809790' app/views/compute_resources/vms/show.html.erb:1:in `_app_views_compute_resources_vms_show_html_erb__620887415_70269412946320_0' app/controllers/compute_resources/vms_controller.rb:26:in `show' </pre> The Libvirt host has various storage pools, sich as a LVM volume group called "virthosts" or a filesystem directory called "cd_images", but no "default" storage pool. Using Libvirt 0.9.8 on Ubuntu 12.04, Foreman 0.5-nightly-ba71c565. This seems related to the fact that Foreman seems to think every VM's disk is based off the "default" storage pool, even when it is not. In our environment, all VMs have their volumes in a "virthost" LVM-based storage pool, not in the "default" storage pool. Nonetheless, for a given VM, Foreman says this about the VM's disk: "using 1G GB out of 10G GB (default storage pool - )". Foreman also seems to think that all disks are 10GB in size, even when they are not. I recall a similar problem in Foreman 0.4.2.