Red Hat Bugzilla – Bug 1314839
image-based provisioning via vmware fails on `wrong number of arguments (2 for 1)`
Last modified: 2016-07-27 05:25:33 EDT
<pre> 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' </pre> 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.
Created from redmine issue http://projects.theforeman.org/issues/14051
Moving to POST since upstream bug http://projects.theforeman.org/issues/14051 has been closed
VERIFIED with sat62-snap4 Image based provisioning was successful with vmware image.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1501