Bug #14051: image-based provisioning via vmware fails on `wrong number of arguments (2 for 1)` - Foreman

Actions

Copy link

Bug #14051

closed

image-based provisioning via vmware fails on `wrong number of arguments (2 for 1)`

Added by Ivan Necas almost 9 years ago. Updated over 6 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Compute resources - VMware

Target version:

1.11.0

Difficulty:

Triaged:

Bugzilla link:

1314839

Pull request:

Fixed in Releases:

Found in Releases:

1.11.0

Red Hat JIRA:

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.

Related issues 1 (0 open — 1 closed)