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.
Created attachment 1611200[details]
foreman debug
Description of problem:
When I specified Datastore config in compute profile it is not used when creating a VMware VM.
Version-Release number of selected component (if applicable): 6.6 snap 18
How reproducible:
Steps to Reproduce:
1. Create compute resource for vcenter
2. Create Compute profile tied to a Datastore (mine happened to be a local esxi datastore).
3. Create host group with compute profile (dont think this is required)
4. Create VM with hostgroup
Actual results:
Storage config does not appear in "Virtual Machine" tab and when the I press submit the following error occurs:
Failed to create a compute toledovcenter (VMware) instance toby-lutkins.vmdomain.com: InvalidDatastorePath: Invalid datastore path '[datastore1]'.
Expected results:
VM is created on data store.
Additional info:
Screen recording here
https://drive.google.com/file/d/1gFdgUWM3r0nvW33pZE_cCkRB1ESfj0Sn/view?usp=sharing
Also, I created a host manually and specified the datastore in the "VM" tab directly and I was able to create the VM.
Upstream issue was closed as a duplicate of 27764
which is assigned to bz 1724780. Closing this as a duplicate too.
*** This bug has been marked as a duplicate of bug 1724780 ***