Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
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 ***
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: