Project

General

Profile

Actions

Bug #20336

closed

OS created automatically after syncing the kickstart repo is not assigned to the provisioning templates

Added by Justin Sherrill over 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Repositories
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

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

Description of problem:
The OS which is automatically created after syncing an OS repo (kicstart) is not automatically assigned to any Provisioning templates.
The pre-created OS (e.g. rhel7.3 if the satellite runs on it) contains these associations and the appropriate templates are pre-selected.

Also, If user creates the known OS manually (e.g. RHEL 5.10), these associations are made.

Version-Release number of selected component (if applicable):
satellite-6.3.0-16.0.beta.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. sync a kicstart repo of OS that isn't listed in the Operating Systems yet
2. assert the appt OS has been created
3. check the 'templates' section of the OS (you can compare it with the defaul precreated RHEL os, eventually you can create your own RHEL OS to confirm, the templates are automatically assigned)

Actual results:
no templates associated

Expected results:
since the OS is known, it should have the all applicable templates associated and pre-selected

Additional info:
i chose the "Other" component, since i wasn't sure, whether this is 'Repository' or 'Provisioning Templates'

Actions

Also available in: Atom PDF