Bug #29901: Default job templates are not locked - Foreman Remote Execution - Foreman

Actions

Copy link

Bug #29901

closed

Default job templates are not locked

Added by Leos Stejskal about 5 years ago. Updated about 5 years ago.

Status:

Closed

Priority:

High

Assignee:

Category:

Target version:

Difficulty:

Triaged:

Bugzilla link:

1830253

Pull request:

https://github.com/theforeman/foreman/pull/7691, https://github.com/theforeman/foreman_remote_execution/pull/500

Fixed in Releases:

foreman_remote_execution 3.3.0

Found in Releases:

Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1830253

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: