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:
In the satellite 6.8 release, we can see the MS Windows provisioning Templates are available, as we don't support provisioning Windows servers from the RedHat satellite, so remove the MS Windows provisioning Templates from the satellite server.
Version-Release number of selected component (if applicable):
Satellite 6.8
How reproducible:
100%
Steps to Reproduce:
Execute the command to pull the templates
hammer> template list --search "name ~ Windows"
----|---------------------------|----------
ID | NAME | TYPE
----|---------------------------|----------
214 | Windows default finish | finish
215 | Windows default iPXE | iPXE
216 | Windows default provision | provision
213 | Windows default PXELinux | PXELinux
220 | Windows network | snippet
217 | Windows peSetup.cmd | script
----|---------------------------|----------
Expected results:
As we don't support provisioning windows servers from the RedHat Satellite, so removing these templates will reduce confusion.
Additional info:
The program has decided to go with the following changes in order to address this BZ:
1) As a user when I enter the provisioning templates list, by default I only want to see the supported RH templates
2) As a user on the template list I want to recognize the RH supported template by the RH icon on the row for a given template.
3) As a user I want to be able to enable implicit listing all templates (meaning also not-supported) in the Provisioning settings
VERIFIED
@Satellite 7.0.0 snap 14
rubygem-foreman_theme_satellite-9.0.0.5-1.el8sat.noarch
foreman-3.1.1.9-1.el8sat.noarch
1) By default user can see all provisioning templates - supported and non-supported
2) Every shipped provisioning template has a description with the exception of 5 templates - BZ2073468 , BZ2073469
3) Users can hide non-supported templates from the list by changing a setting. There is also a search capability `supported = true` which allows the user to filter out the supported templates. Implemented as a part of BZ2045504.
4) Every supported provisioning template has a Red Hat logo icon
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2022:5498