Bug 593940 - Configuration channels in activation key are not added to systems
Configuration channels in activation key are not added to systems
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Configuration Management (Show other bugs)
All Linux
low Severity high
: ---
: ---
Assigned To: Tomas Lestach
Red Hat Satellite QA List
Depends On:
Blocks: 462714
  Show dependency treegraph
Reported: 2010-05-20 01:20 EDT by Paul Wayper
Modified: 2017-07-19 06:07 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-07-19 06:07:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Paul Wayper 2010-05-20 01:20:50 EDT
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 06:07:59 EDT
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

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