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):
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 ->
Steps 2. or 3. seems redundant to me
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?)
Created redmine issue http://projects.theforeman.org/issues/6370 from this bug
*** Bug 1144004 has been marked as a duplicate of this bug. ***
*** Bug 1120716 has been marked as a duplicate of this bug. ***
Starting with 6.1 (and already in Katello 2.0), the situation is improved a little.
When an operating system with a distribution is synchronized for the first time, the dual associations will be made and there's no steps for the user.
In the Settings (Katello tab), you may configure which templates are used for those initial associations if you want to use your own.
The underlying usability issue still needs to be resolved though, especially if the one wants to provision an OS that's content doesn't come from Katello.
Upstream bug component is WebUI
Upstream bug component is Provisioning Templates
I'm lowering severity to medium. It is serious usability issue but once it's set it doesn't disrupt any operation.
This has been copied to an issue upstream. When the upstream issue is fixed, the next version of satellite will contain it. We will no longer track this downstream.
For the record, this upstream ticket should make the UX better: https://projects.theforeman.org/issues/23923