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 2186114

Summary: Provisioning vm on VMware data store cluster using API fails with error InvalidDatastorePath: Invalid datastore path
Product: Red Hat Satellite Reporter: Yogendra <yyadav>
Component: Compute Resources - VMWareAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: sganar
Severity: high Docs Contact:
Priority: high    
Version: 6.11.4CC: chrobert, gisoni, gtalreja, lstejska, mhulan
Target Milestone: streamKeywords: MigratedToJIRA, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: fog-vsphere 3.6.5 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:12:52 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:

Description Yogendra 2023-04-12 06:35:14 UTC
Description of problem:
 
  - When provisioning hosts on Vmware data store cluster using API fail with error InvalidDatastorePath: Invalid datastore path  '[clustername]'. 

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

  - Red Hat Satellite Version 6.11

How reproducible:

  - Specify data store cluster which contains multiple pods in Compute resource and then try to provision host using api

Steps to Reproduce:

  1. WebUI -> Infrastructure -> Compute Profile -> select any -> select your compute resource -> go to section Storage -> Specify Datastore cluster which contains multiple pods.

  2. Now try to provision hosts using api and it fails with error InvalidDatastorePath: Invalid datastore path

  3. If we try to provision hosts on VMware  data store cluster using Red Hat Satellite Web UI it is completed successfully.

Actual results:

  - API Provision fails with error InvalidDatastorePath: Invalid datastore path  '[clustername].

Expected results:

  - Hosts provision should complete without error.

Additional info:

  - When specified with datastore specific pod api provisioning is working.

Comment 3 sganar 2024-05-22 15:19:16 UTC
Verified.

Tested on Satellite stream Snap 60
rubygem-fog-vsphere-3.6.5

Steps followed: 
1. Configure the Satellite for provisioning
2. Create VMware CR
3. Provision a host via API and use `storage_pod` as a key while passing datastore cluster instead of datastore

Observation:
Host build was submitted and provisioning was successful.
Also when no datastore or storage pod is given appropriate error message is to specify the datastore/cluster

Comment 4 Eric Helms 2024-06-06 16:12:52 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.