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.
Description of problem:
Provisioning to VMware from template image fails if Datastore Cluster selected in compute profile.
How reproducible:
Very
Steps to Reproduce:
1. Create VMware compute profile with "Datastore Cluster" selected, you will see "Data Store" select box gets disabled.
2. Navigate to New host page, select deploy on VMware with created compute profile.
3. Navigate to "Virtual Machine" tab, you will see both "Datastore cluster" and "Data store" select boxes enabled
Actual results:
Error: Unable to save
Failed to create compute instance: InvalidArgument: A specified parameter was not correct: Datastore outside the pod is specified for a disk to be placed inside the pod.
Host parameters in foreman/production.log contain both "storage_pod" and "datastore" values.
Expected results:
Host creation should succeed.
I think host parameters should only contain either "storage_pod" or "datastore" values, not both.
Additional info:
This probably happens because the disabling of "Data Store" select box on compute_profile form is controlled by onChange event on "Datastore cluster" select box and 'ContentLoad' trigger which is triggered in application.js. When this form is called by ajax by the "New host" form that trigger is not triggered and "Data Store" select box remains enabled.
If some other "Datastore cluster" is selected and then the original one is reselected the "Data store" select box gets disabled (by the onChange event) and installation succeeds.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.