Bug 1210394 - First synchronized Kickstart repo does not get associated to provisioning templates
Summary: First synchronized Kickstart repo does not get associated to provisioning tem...
Keywords:
Status: CLOSED DUPLICATE of bug 1251041
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-09 15:15 UTC by Og Maciel
Modified: 2015-12-03 16:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-02 19:36:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
template missing os association (169.77 KB, image/png)
2015-04-09 15:15 UTC, Og Maciel
no flags Details

Description Og Maciel 2015-04-09 15:15:52 UTC
Created attachment 1012721 [details]
template missing os association

Description of problem:

I usually synchronize the Kickstart repositories for the following OS versions

* RHEL 7.1
* RHEL 6.6 x86_64
* RHEL 6.6 i386
* RHEL 5.11 x86_64
* RHEL 5.11 i386

I noticed that the first of the kickstart repositories I enabled our of the ones listed above does not get automatically associated to the required/default provisioning templates such as the Satellite Kickstart Default template. All other OSes do get associated except for the first one I enable.


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

* Sat 6.1 RC4

How reproducible:


Steps to Reproduce:
1. Enable several different kickstart repositories and synchronizing them
2. Once they're synchronized, create content views with them and publish/promote
3. Now visit the provisioning templates and look at the Satellite Kickstart Default template, checking if all OSes have been associated with it.

Actual results:

Usually the first OS I enable doesn't get associated

Expected results:


Additional info:

Comment 2 Brad Buckingham 2015-09-02 19:36:36 UTC
Investigated and this looks like an issue we also saw on RHCI.  Closing this one as a duplicate.

*** This bug has been marked as a duplicate of bug 1251041 ***


Note You need to log in before you can comment on or make changes to this bug.