Bug 1489516

Summary:	List only the data stores under a selected vmware cluster while provisioning a host instead of entire datacenter.
Product:	Red Hat Satellite	Reporter:	Varatharaja Perumal G <vgunasek>
Component:	Compute Resources - VMWare	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Vladimír Sedmík <vsedmik>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.6.0	CC:	bkearney, chrobert, egolov, lhellebr, mhulan, mjia, mverma, vsedmik
Target Milestone:	6.6.0	Keywords:	Reopened, Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	foreman-1.22.0-0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 21:25:43 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:
Bug Depends On:
Bug Blocks:	1620176

Description Varatharaja Perumal G 2017-09-07 15:21:30 UTC

Description of problem:

In Satellite create a VMware resource. The account used to connect to vcenter has full access to 4 ESX Cluster. Let's call then Cluster A, B, C and D.

When we create a new compute profile on VMware resource by selecting a cluster this profile belongs to, say Cluster A. However we choosing a storage datastore we can see every datastore from all 4 clusters. It's creating complication on selecting the correct information since the datastore from cluster B, C and D are not available on Cluster A. 

Version-Release number of selected component (if applicable):

Satellite 6.2.11

Actual results:

Listing all the data store available in the cluster

Expected results:

List the data store from a selected cluster instead of the entire data center.

Additional info:

Comment 2 Marek Hulan 2017-10-27 18:39:46 UTC

So selecting a cluster should basically limit what datastores and datastores clusters we display in the form for compute profile and host form.

Comment 4 Bryan Kearney 2019-02-20 17:07:39 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/2113 has been resolved.

Comment 5 Ondřej Ezr 2019-06-04 09:39:45 UTC

*** Bug 1426592 has been marked as a duplicate of this bug. ***

Comment 8 Bryan Kearney 2019-10-22 19:51:24 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

Comment 11 Bryan Kearney 2019-11-05 20:28:15 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/2113 has been resolved.