Bug #6370
closedassigning provisioning template to operating system is not straight forward
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?)
Updated by Dominic Cleal over 10 years ago
- Category set to Templates
- Assignee deleted (
Dominic Cleal)
foreman_setup helps a lot here for setting up the first OS.
Updated by David Schmitt over 10 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.
Updated by Stephen Benjamin over 10 years ago
- Related to Tracker #6631: Provisioning Template Improvements added
Updated by The Foreman Bot over 10 years ago
- Status changed from New to Ready For Testing
- Target version set to 1.7.5
- Pull request https://github.com/theforeman/foreman/pull/1662 added
Updated by Anonymous about 10 years ago
- Target version changed from 1.7.5 to 1.7.4
Updated by Anonymous about 10 years ago
- Target version changed from 1.7.4 to 1.7.3
Updated by Dominic Cleal about 10 years ago
- Target version changed from 1.7.3 to 1.7.2
Updated by Stephen Benjamin about 10 years ago
- Status changed from Ready For Testing to New
Updated by The Foreman Bot about 10 years ago
- Status changed from New to Ready For Testing
Updated by Dominic Cleal about 10 years ago
- Status changed from Ready For Testing to New
- Target version deleted (
1.7.2)
Updated by Markus Frosch almost 10 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?
Updated by Tomáš Strachota about 8 years ago
- Description updated (diff)
- Target version set to 115
Updated by Lukas Zapletal over 6 years ago
- Status changed from New to Duplicate
I am gonna work on this as part of #23923 so closing for now.