Bug 1210394
| Summary: | First synchronized Kickstart repo does not get associated to provisioning templates | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Og Maciel <omaciel> | ||||
| Component: | Provisioning | Assignee: | Katello Bug Bin <katello-bugs> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Katello QA List <katello-qa-list> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.1.0 | CC: | bbuckingham | ||||
| Target Milestone: | Unspecified | Keywords: | Triaged | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-09-02 19:36:36 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
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: