Created attachment 1608722 [details]
Failed to create a compute test (VMware) instance tammy-arnzen.toledo.satellite.lab.eng.rdu2.redhat.com: wrong number of arguments (given 2, expected 1)
2019-08-27T16:40:18 [W|app|09a39f98] Failed to create a compute test (VMware) instance tammy-arnzen.toledo.satellite.lab.eng.rdu2.redhat.com: wrong number of arguments (given 2, expected 1)
ArgumentError: wrong number of arguments (given 2, expected 1)
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27719 has been resolved.
Needs bump of fog-vsphere to v3.2.1 or cherry-pick https://github.com/fog/fog-vsphere/commit/d520c5f429dae30ccdbf475351368d051268993b
@ Satellite 6.6 snap 16
1. Attempt to provision a VM on VMWare.
2. Select 1 disk from DataStore.
3. Select another from Storage Pod - iSCSI cluster.
4. Provision the VM.
1. VM is provisioned but both the disks are assigned from non-selected(while provisioning) data store.
2. This also includes the iSCSI cluster storage pod disk is not being selected.
Attaching before and after screenshots disks selected on provisioning.
# Note: Even at VMWare end these disk mismatch is happening, so it's not only satellite end UI issue.
Created attachment 1613190 [details]
Before and After mismatch in Datastore/Cluster selection
I believe this is not an issue in scope of this BZ, could you please create new one for this issue?
As per comment 8, this bug is fixed as we didn't observe the issue/error mentioned in the description of this bug.
But as per comment 8 and comment 10, we found another issue for which new bug is filled here - https://bugzilla.redhat.com/show_bug.cgi?id=1750758 and this issue is out of the scope of this bug.
Hence moving the status of this bug to Verified.
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.