Bug 1907795 - Remove the MS Windows provisioning Templates from the RedHat Satellite 6
Summary: Remove the MS Windows provisioning Templates from the RedHat Satellite 6
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning Templates
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.11.0
Assignee: Oleh Fedorenko
QA Contact: Ondrej Gajdusek
URL:
Whiteboard:
: 1904166 1998082 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-15 09:29 UTC by Satyajit Das
Modified: 2024-03-25 17:33 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-05 14:28:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-4239 0 None None None 2021-10-11 13:15:18 UTC
Red Hat Issue Tracker SAT-4240 0 None None None 2021-10-11 13:15:18 UTC
Red Hat Issue Tracker SAT-4241 0 None None None 2021-10-11 13:15:18 UTC
Red Hat Product Errata RHSA-2022:5498 0 None None None 2022-07-05 14:28:45 UTC

Description Satyajit Das 2020-12-15 09:29:38 UTC
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:

Comment 2 Sayan Das 2021-08-26 12:05:09 UTC
*** Bug 1998082 has been marked as a duplicate of this bug. ***

Comment 4 Marek Hulan 2021-10-11 12:32:23 UTC
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

Comment 5 Ron Lavi 2021-12-01 13:36:40 UTC
*** Bug 1904166 has been marked as a duplicate of this bug. ***

Comment 8 Ondrej Gajdusek 2022-04-08 15:01:37 UTC
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

Comment 11 errata-xmlrpc 2022-07-05 14:28:38 UTC
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


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