Bug 593940

Summary: Configuration channels in activation key are not added to systems
Product: Red Hat Satellite 5 Reporter: Paul Wayper <paulway>
Component: Configuration ManagementAssignee: Tomas Lestach <tlestach>
Status: CLOSED EOL QA Contact: Red Hat Satellite QA List <satellite-qa-list>
Severity: high Docs Contact:
Priority: low    
Version: 530   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-19 10:07:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 462714    

Description Paul Wayper 2010-05-20 05:20:50 UTC
Description of problem:

Any configuration channel that has been added to an activation key is not actually applied to a system that installs using that activation key.

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


How reproducible:

Always - two different people tested it.

Steps to Reproduce:
1. Create a configuration channel
2. Create an activation key
3. Add the configuration channel to the activation key (Activation key -> Configuration -> Subscribe to channels -> Select channel and confirm)
4. Save changes.
5. Create a kickstart file that uses that activation key.
6. Boot a remote machine off that kickstart file.
Actual results:

Client has no configuration channels available.

Expected results:

Client should have configuration channel available.  In Systems, selecting the installed system and then choosing Configuration from the system menu should show the configuration channel already added to the system.

Additional info:

Comment 1 Tomas Lestach 2017-07-19 10:07:59 UTC
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.
We're closing this Bugzilla due to the Satellite 5 version this bug was reported against having been EOL (End-of-Life) [1].
Please re-open if the issue still exists in the latest Satellite 5 version.

[1] Satellite Life Cycle page: https://access.redhat.com/support/policy/updates/satellite