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.

Bug 1830253

Summary: Default job templates are not locked
Product: Red Hat Satellite Reporter: Kenny Tordeurs <ktordeur>
Component: Remote ExecutionAssignee: Leos Stejskal <lstejska>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: high Docs Contact:
Priority: high    
Version: 6.7.0CC: aruzicka, egolov, inecas, jjeffers, lstejska, mawerner, mhulan, ofedoren, pcreech
Target Milestone: 6.8.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_remote_execution-3.3.0,tfm-rubygem-katello-3.16.0.1-1, tfm-rubygem-foreman_openscap-4.0.3 Doc Type: Known Issue
Doc Text:
Default job templates are not locked
 Story Points: ---
Clone Of:
: 1862260 (view as bug list) Environment:
Last Closed: 2020-10-27 13:02:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
sat65
none
sat67
none
sat66
none
6.8-initial-fix
none
6.8-oscap none

Description Kenny Tordeurs 2020-05-01 10:45:00 UTC 
Description of problem:
Default templates are not locked as indicated in the documentation:
~~~
Satellite provides default job templates that you can use for executing jobs. To view the list of job templates, navigate to Hosts > Job templates. If want to use a template without making changes, proceed to Section 10.6.2, “Executing Jobs”.

You can use default templates as a base for developing your own. Default job templates are locked for editing. Clone the template and edit the clone.

To clone a template, in the Actions column, select Clone.
Enter a unique name for the clone and click Submit to save the changes.
~~~

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.7/html-single/managing_hosts/index#sect-Managing_Hosts-Configuring_and_Running_Remote_Commands

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

How reproducible:
100 %

Steps to Reproduce:
1. Go to job templates
2.
3.

Actual results:
No templates are locked

Expected results:
Default templates to be locked

Additional info:
Comment 3 Kenny Tordeurs 2020-05-01 10:48:14 UTC 
Created attachment 1683643 [details]
sat65

In Satellite 6.5 we can see that some job templates are locked
Comment 4 Kenny Tordeurs 2020-05-01 10:48:54 UTC 
Created attachment 1683644 [details]
sat67

No locked job templates in Satellite 6.7
Comment 5 Kenny Tordeurs 2020-05-01 11:09:51 UTC 
Created attachment 1683651 [details]
sat66

Satellite 6.6 also has no locked job templates
Comment 7 Leos Stejskal 2020-05-21 07:59:22 UTC 
Created redmine issue https://projects.theforeman.org/issues/29901 from this bug
Comment 8 Bryan Kearney 2020-05-28 16:02:49 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29901 has been resolved.
Comment 9 Peter Ondrejka 2020-06-19 08:17:07 UTC 
Checked in Sat 6.8 snap 8, seems that Katello related templates didn't get the default lock, see attachment
Comment 10 Peter Ondrejka 2020-06-19 08:18:59 UTC 
Created attachment 1698058 [details]
6.8-initial-fix
Comment 11 Leos Stejskal 2020-06-19 08:23:28 UTC 
Locking Katello templates is done in this PR: https://github.com/Katello/katello/pull/8736 (not merged yet),
they are not part of Remote Execution plugin.
Comment 12 Adam Ruzicka 2020-07-14 13:24:59 UTC 
Katello PR was merged, moving to POST.
Comment 14 Peter Ondrejka 2020-09-04 11:32:36 UTC 
Created attachment 1713767 [details]
6.8-oscap
Comment 15 Peter Ondrejka 2020-09-04 11:34:41 UTC 
There seems to be one remaining unlocked default template: Run OpenSCAP scans, see attachment
Comment 17 Marek Hulan 2020-09-08 07:42:14 UTC 
Upstream packaging PR opened at https://github.com/theforeman/foreman-packaging/pull/5773, cleaning whiteboard as it needs new rebase.
Comment 18 James Jeffers 2020-09-09 11:03:49 UTC 
*** Bug 1874153 has been marked as a duplicate of this bug. ***
Comment 19 Peter Ondrejka 2020-09-14 08:52:41 UTC 
Verified on Satellite 6.8 snap 15
Comment 22 errata-xmlrpc 2020-10-27 13:02:11 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 (Important: Satellite 6.8 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-2020:4366