Bug 1467709 - When provisioning a new host, the compute profile settings are not honoured.
Summary: When provisioning a new host, the compute profile settings are not honoured.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.2.10
Hardware: All
OS: Linux
high
high
Target Milestone: Unspecified
Assignee: Ondřej Ezr
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-04 17:37 UTC by Varatharaja Perumal G
Modified: 2023-09-07 18:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-03 18:58:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Varatharaja Perumal G 2017-07-04 17:37:44 UTC
Description of problem:

When provisioning a new host we use a host group associated with compute profile. After submitting it fail to use the correct image template provided in the UI and give below error. 

"Failed to create a compute VMware (VMware) instance host.example.local: CannotAccessVmConfig: Unable to access the virtual machine configuration: Unable to access file [SAN] "

We found out that this error is due to the image being in the wrong cluster. That means that Satellite changes the selected image under "Operating System" after clicking "Submit". It switches back to a different Image.

Provisioning works when we manually fill the host details/when we change the image manually after it fails.

So, the "Image" and "Network" settings from the Compute profile settings do not work when provisioning a new host.


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

How reproducible:

Only reproducible in customer end.

Actual results:

Provision fails to use the correct image associated with the compute profile.

Expected results:

Should be able to provision the host using the image associated with compute profile.

Additional info:

debug logs are attached in case.

Comment 4 Marek Hulan 2017-07-13 10:43:05 UTC
Varatharaja, if the configuration is used from a different compute profile then it's likely the same cause and this BZ can be used.

Comment 6 Daniel Lobato Garcia 2018-02-23 13:17:26 UTC
This is being fixed upstream.

https://github.com/theforeman/foreman/pull/3559

Comment 7 Daniel Lobato Garcia 2018-02-23 13:18:20 UTC
Connecting redmine issue http://projects.theforeman.org/issues/2113 from this bug

Comment 11 Marek Hulan 2019-01-29 15:32:49 UTC
The redmine issue only track datastore, networks will be separate fix.

Comment 13 Bryan Kearney 2019-08-05 12:22:34 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 14 Bryan Kearney 2019-09-03 18:58:31 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.


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