Bug 1489516 - List only the data stores under a selected vmware cluster while provisioning a host instead of entire datacenter.
Summary: List only the data stores under a selected vmware cluster while provisioning ...
Status: ON_QA
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.2.11
Hardware: All
OS: Linux
medium
medium vote
Target Milestone: 6.6.0
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Keywords: Triaged
: 1426592 (view as bug list)
Depends On:
Blocks: 1620176
TreeView+ depends on / blocked
 
Reported: 2017-09-07 15:21 UTC by Varatharaja Perumal G
Modified: 2019-06-05 03:19 UTC (History)
5 users (show)

(edit)
Clone Of:
(edit)
Last Closed:


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 2113 None None None 2017-10-27 18:41 UTC

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. ***


Note You need to log in before you can comment on or make changes to this bug.