Bug 2186114 - Provisioning vm on VMware data store cluster using API fails with error InvalidDatastorePath: Invalid datastore path
Summary: Provisioning vm on VMware data store cluster using API fails with error Inva...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.11.4
Hardware: x86_64
OS: Linux
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-12 06:35 UTC by Yogendra
Modified: 2023-06-29 21:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-18721 0 None None None 2023-06-29 21:01:26 UTC
Red Hat Knowledge Base (Solution) 7016290 0 None None None 2023-06-29 20:59:27 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.