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 1613042 - Satellite shows wrong template while resolving provisioning templates.
Summary: Satellite shows wrong template while resolving provisioning templates.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning Templates
Version: 6.3.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Roman Plevka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-06 20:26 UTC by Onkar
Modified: 2023-09-07 19:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-03 22:57:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 24666 0 Normal New Foreman shows wrong template while resolving provisioning templates. 2020-12-04 17:09:01 UTC

Description Onkar 2018-08-06 20:26:53 UTC 
Description of problem:
Provision by using the Custom template. It should show Custom template name but it resolved to " Satellite Kickstart Default ". So it is showing wrong information.

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


How reproducible:


Steps to Reproduce:
1. Create a Custom template.
2. Try to provision hosts. 
3. Under the Operating System tab, click on Resolve Button.

Actual results: It displays Satellite Kickstart Default.


Expected results:
It should show Custom template name.

Additional info:
Comment 1 Marek Hulan 2018-08-07 06:00:18 UTC 
How did you assign the template? Just creating custom template is of course not enough. You need to edit OS and choose this template for the given template type.
Comment 2 Vladimir Vasilev 2018-08-07 12:10:45 UTC 
Marek, I put the appropriate OS, host group and environment on "Association" tab on the provisioning template. I do NOT want to set this as default template by editing the OS and choosing the custom template.
Comment 4 Ondřej Pražák 2018-08-20 11:23:54 UTC 
Based on the comment #2, the Custom template is associated to OS, but not set to be used by editing the OS. My understanding is that you would like to choose the Custom template as an override when creating a host while having "Satellite Kickstart Default" as a default option. 

We already track the same request as #1514168, therefore I will close this as a duplicate. Feel free to reopen if I misunderstood.

*** This bug has been marked as a duplicate of bug 1514168 ***
Comment 5 Ondřej Pražák 2018-08-21 06:33:06 UTC 
It was discovered that this is not a duplicate after all. Reproducing steps:

1) Create 2 hostgroups A and B, configure them with everything needed to provision a host, both of them having the same OS named 'MyOS'
2) Create a custom Provisioning template named 'Custom'
3) Associate Custom template to the MyOS, in the 'Valid Host Group and Environment Combinations' select B as a hostgroup and Puppet env 'production', do not edit the MyOS and leave 'Kickstart default' set as provisioning template
4) Try to create a host with hostgroup and Puppet env matching those configured in previous step (B and production)
5) Hit the resolve button, 'Kickstart default' will be resolved as a provisioning template
6) create host, go to edit, resolve the templates again, now provisioning template resolves to Custom and host got actually deployed with this template
7) Do the same for hostgroup A - template resolves correctly each time as the combination from step 4 does not match this case

It is expected that template resolves correctly each time.
Comment 6 Ondřej Pražák 2018-08-21 06:39:49 UTC 
Created redmine issue http://projects.theforeman.org/issues/24666 from this bug
Comment 7 Bryan Kearney 2020-02-03 16:37:35 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 8 Bryan Kearney 2020-03-03 22:57:26 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.