Bug #6370

assigning provisioning template to operating system is not straight forward

Added by Dominic Cleal about 3 years ago. Updated 12 months ago.

Status:New
Priority:Normal
Assigned To:-
Category:Templates
Target version:Team Marek backlog
Difficulty: Bugzilla link:1107743
Found in release: Pull request:https://github.com/theforeman/foreman/pull/1662
Story points-
Velocity based estimate-

Description

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

Description of problem:
Assigning provisioning template to operating system is not straight forward - requires multiple steps which seems redundant to me and if they are not, there is not enough inline help/tips helping to explain the problem

Version-Release number of selected component (if applicable):
foreman 1.12

How reproducible:
always

Steps to Reproduce:
1. Create operating system
2. Hosts -> Provisioning templates -> Kickstart default user data ->
-> Association -> check checkbox nex to <your_operating_system> -> Submit
3. Hosts -> Operating systems -> <your_operating_system> -> Templates ->
-> select "Kickstart default user data" in "user_data" drop-down element ->
-> Submit

Actual results:
Steps 2. or 3. seems redundant to me

Expected results:
One of steps 2. or 3. might be redundant, or webUI could be altered to help me to understand this is needed (e.g. some hints added?)


Related issues

Related to Foreman - Tracker #6631: Provisioning Template Improvements New 07/16/2014

History

#1 Updated by Dominic Cleal about 3 years ago

  • Category set to Templates
  • Assigned To deleted (Dominic Cleal)

foreman_setup helps a lot here for setting up the first OS.

#2 Updated by David Schmitt about 3 years ago

I've noticed this redundancy too. While foreman_setup helps with the first, it is still a stumbling block for all the other OS/template associations that will be configured.

#3 Updated by Stephen Benjamin about 3 years ago

  • Related to Tracker #6631: Provisioning Template Improvements added

#4 Updated by The Foreman Bot about 3 years ago

  • Status changed from New to Ready For Testing
  • Target version set to Sprint 27
  • Pull request https://github.com/theforeman/foreman/pull/1662 added

#5 Updated by Dmitri Dolguikh almost 3 years ago

  • Target version changed from Sprint 27 to Sprint 28

#6 Updated by Dmitri Dolguikh almost 3 years ago

  • Target version changed from Sprint 28 to Sprint 29

#7 Updated by Dominic Cleal almost 3 years ago

  • Target version changed from Sprint 29 to Sprint 30

#8 Updated by Stephen Benjamin almost 3 years ago

  • Status changed from Ready For Testing to New

#9 Updated by The Foreman Bot almost 3 years ago

  • Status changed from New to Ready For Testing

#10 Updated by Dominic Cleal almost 3 years ago

  • Status changed from Ready For Testing to New
  • Target version deleted (Sprint 30)

#11 Updated by Markus Frosch over 2 years ago

Wouldn't it be the easiest way to use the OSfamily?

  • Template -> OSfamily
  • OS -> Template

Question is how to do the migration, lookup OS references in template, and replace by OSfamily link?

Or keep the old behavior invisibly available?

#12 Updated by Tomáš Strachota 12 months ago

  • Description updated (diff)
  • Target version set to Team Marek backlog

Also available in: Atom PDF