Project

General

Profile

Bug #19677

Unable to edit localboot templates

Added by Lukas Zapletal about 2 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
High
Category:
Templates
Target version:
Difficulty:
Triaged:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Our recent change in template locking caused that users are no longer able to edit "default local boot" templates as this name is hardcoded in app/models/concerns/orchestration/tftp.rb. We need to make a configuration option for that so user can change this, since kind is different for each individual template type, the default value would need to be something like "%KIND% default local boot".

Additionally we can make a small change to attempt to read host variable called "localboot_template" and if set, let's use that. This will help to workaround issues with local booting, some hardware or VMs do not boot via LOCALBOOT option and need to use COM32 chainloader (see #6725) and this small change will allow to change this behavior per host.

I will also make a change in community-templates so some comment help text is available for users.

This is a 1.15 backport candidate, this is a high priority for provisioning.


Related issues

Related to Foreman - Bug #18639: All templates that are shipped with Foreman should be locked by defaultClosed2017-02-23
Related to Foreman - Feature #17228: Allow selecting a template used as global default for each kindClosed2016-11-04

Associated revisions

Revision 0e8f2cac (diff)
Added by Ondřej Pražák about 2 years ago

Fixes #19677 - Add settings for local boot templates

Revision 69677033 (diff)
Added by Ondřej Pražák about 2 years ago

Fixes #19677 - Add settings for local boot templates

(cherry picked from commit 0e8f2cac4ed72ddf819582700977a4b6844a7c06)

History

#1 Updated by Dominic Cleal about 2 years ago

  • Related to Bug #18639: All templates that are shipped with Foreman should be locked by default added

#2 Updated by Dominic Cleal about 2 years ago

  • Related to Feature #17228: Allow selecting a template used as global default for each kind added

#3 Updated by Marek Hulán about 2 years ago

A simple workaround is to unlock the template but I agree we should fix it properly. I think the template selection should be in settings so it's consistent with how we allow to select default PXE template (#17228). The override through params would be nice since Settings is global and can't be scoped per organizations.

#4 Updated by The Foreman Bot about 2 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Ondřej Pražák
  • Pull request https://github.com/theforeman/foreman/pull/4570 added

#5 Updated by Marek Hulán about 2 years ago

  • Target version set to 1.14.0

#6 Updated by Marek Hulán about 2 years ago

  • Target version changed from 1.14.0 to 1.14.3

#7 Updated by Anonymous about 2 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#8 Updated by Daniel Lobato Garcia about 2 years ago

  • Legacy Backlogs Release (now unused) set to 276

Also available in: Atom PDF