Bug 1323548 - Parent Software Channel isn't used during kickstart install
Summary: Parent Software Channel isn't used during kickstart install
Keywords:
Status: CLOSED EOL
Alias: None
Product: Spacewalk
Classification: Community
Component: Documentation
Version: 2.4
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-04 02:52 UTC by Lachlan
Modified: 2020-03-13 13:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-13 13:30:07 UTC


Attachments (Terms of Use)

Description Lachlan 2016-04-04 02:52:34 UTC
Document URL: 

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/html-single/Getting_Started_Guide/index.html

Section Number and Name: 

Depends on internal needs. It's related to Kickstart, but based around the idea of the Parent/Child Channel.

Describe the issue: 

During Kickstart installations, the Parent, or base, channel, isn't used. So it is considered less a channel and more a way of grouping child channels. 



Suggestions for improvement: 

This needs to be made explicit.

For example, if you have a base or Parent channel called "centos_7" you need to have a child channel called "centos_7_base" which has the Base packages available. 

If you do not have this set up, the kickstarted installation will fail with the message:


You have requested that the package 'x' should be installed. This package does not exist. Would you like to ignore this package and continue with the installation?'

(in this case x= hwloc-devel, but I think that's irrelevant' - if I answer yes, it just asks for every package)

Comment 1 Stefan Bluhm 2019-10-16 10:15:38 UTC
Note the resulting bug IDs for the impact:
https://bugzilla.redhat.com/show_bug.cgi?id=1713283
https://bugzilla.redhat.com/show_bug.cgi?id=1758286

Comment 2 Michael Mráka 2020-03-13 13:30:07 UTC
Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.


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