Actions
Bug #14051
closed
image-based provisioning via vmware fails on `wrong number of arguments (2 for 1)`
Description
ArgumentError: wrong number of arguments (2 for 1) | /home/inecas/.rbenv/versions/2.1.0/lib/ruby/gems/2.1.0/gems/fog-vsphere-0.6.0/lib/fog/vsphere/requests/compute/create_vm.rb:74:in `get_storage_pod' | /home/inecas/.rbenv/versions/2.1.0/lib/ruby/gems/2.1.0/gems/fog-vsphere-0.6.0/lib/fog/vsphere/requests/compute/vm_clone.rb:23:in `vm_clone_check_options' | /home/inecas/.rbenv/versions/2.1.0/lib/ruby/gems/2.1.0/gems/fog-vsphere-0.6.0/lib/fog/vsphere/requests/compute/vm_clone.rb:93:in `vm_clone' | /home/inecas/Projects/ws/foreman-rex/foreman/app/models/compute_resources/foreman/model/vmware.rb:407:in `clone_vm' | /home/inecas/Projects/ws/foreman-rex/foreman/app/models/compute_resources/foreman/model/vmware.rb:354:in `create_vm' | /home/inecas/Projects/ws/foreman-rex/foreman/app/models/concerns/orchestration/compute.rb:76:in `setCompute' | /home/inecas/Projects/ws/foreman-rex/foreman/app/models/concerns/orchestration.rb:162:in `execute' | /home/inecas/Projects/ws/foreman-rex/foreman/app/models/concerns/orchestration.rb:107:in `block in process' | /home/inecas/Projects/ws/foreman-rex/foreman/app/models/concerns/orchestration.rb:99:in `each' | /home/inecas/Projects/ws/foreman-rex/foreman/app/models/concerns/orchestration.rb:99:in `process' | /home/inecas/Projects/ws/foreman-rex/foreman/app/models/concerns/orchestration.rb:35:in `on_save'
The issue was found in fog-vmware (I know about 0.6.0 having it) and has been fixed in https://github.com/fog/fog-vsphere/pull/28, but has not been released yet
at the time of filing this issue.
Updated by Dominic Cleal almost 9 years ago
- Related to Feature #12436: As a user I want to deploy vSphere vms on a storage pods added
Updated by Dominic Cleal almost 9 years ago
- Category set to Compute resources - VMware
- Translation missing: en.field_release set to 71
Updated by Ivan Necas almost 9 years ago
fog-vsphare 0.6.1, just with this feature was just released
Updated by Dominic Cleal almost 9 years ago
- Status changed from New to Resolved
That was quick, thanks! I've built and will tag the RPM for 1.11, source and Debian installations will automatically get the fix.
Actions