Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1746175

Summary: Adding a 2nd disk type of storage_pod/datastore_cluster fails to create vm
Product: Red Hat Satellite Reporter: Chris Roberts <chrobert>
Component: Compute Resources - VMWareAssignee: Ondřej Ezr <oezr>
Status: CLOSED ERRATA QA Contact: Jitendra Yejare <jyejare>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: chrobert, ehelms, mhulan, oezr
Target Milestone: 6.6.0Keywords: Regression, Triaged, UserExperience
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
URL: https://projects.theforeman.org/issues/27719
Whiteboard:
Fixed In Version: fog-vsphere-3.2.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 12:47:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot
none
Before and After mismatch in Datastore/Cluster selection none

Description Chris Roberts 2019-08-27 20:50:28 UTC
Created attachment 1608722 [details]
screenshot

Error:

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)

Traceback:


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)
/opt/theforeman/tfm/root/usr/share/gems/gems/fog-vsphere-3.2.0/lib/fog/vsphere/requests/compute/create_vm.rb:75:in `group_disks_by_storage_pod'
/opt/theforeman/tfm/root/usr/share/gems/gems/fog-vsphere-3.2.0/lib/fog/vsphere/requests/compute/create_vm.rb:55:in `create_vm_on_storage_pod'
/opt/theforeman/tfm/root/usr/share/gems/gems/fog-vsphere-3.2.0/lib/fog/vsphere/requests/compute/create_vm.rb:36:in `create_vm'
/opt/theforeman/tfm/root/usr/share/gems/gems/fog-vsphere-3.2.0/lib/fog/vsphere/models/compute/server.rb:302:in `save'
/usr/share/foreman/app/models/compute_resources/foreman/model/vmware.rb:484:in `create_vm'
/usr/share/foreman/app/models/concerns/orchestration/compute.rb:91:in `setCompute'

Comment 4 Bryan Kearney 2019-09-03 10:01:18 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27719 has been resolved.

Comment 5 Ondřej Ezr 2019-09-03 10:57:46 UTC
Needs bump of fog-vsphere to v3.2.1 or cherry-pick https://github.com/fog/fog-vsphere/commit/d520c5f429dae30ccdbf475351368d051268993b

Comment 8 Jitendra Yejare 2019-09-09 14:42:16 UTC
FailedQA!

@ Satellite 6.6 snap 16

Steps:
----------------

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.


Observation:
----------------
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.

Comment 9 Jitendra Yejare 2019-09-09 14:43:56 UTC
Created attachment 1613190 [details]
Before and After mismatch in Datastore/Cluster selection

Comment 10 Ondřej Ezr 2019-09-10 12:28:16 UTC
Hi Jitendara,

I believe this is not an issue in scope of this BZ, could you please create new one for this issue?

Thanks! :)

Comment 11 Jitendra Yejare 2019-09-10 12:58:28 UTC
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.

Comment 13 errata-xmlrpc 2019-10-22 12:47:58 UTC
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/RHSA-2019:3172