[Spacewalk-list] Best Practice for adding a child Channel?

[Guy Matz]

Hey!  Thanks for the reply!  I'm asking about the scenario in which a
system is already registered and a new child channel is added . . .

On Tue, Jun 11, 2019 at 4:36 PM William Hongach <William.Hongach at marist.edu>
wrote:

> Hello,
>
>
>
> If the child channel is already associated with the activation key at the
> time of client registration, the client should subscribe to the base and
> child channels simultaneously if things are working correctly.  If you want
> to retroactively associate previously registered clients with a newly added
> child channel, I think you may have to script something to process this.
> For example, you can make use of “spacecmd system_addchildchannels” to
> associate the system or system groups with the child channel.
>
>
>
> I’m not sure if “Reactivation” within the GUI using the generated key
> would also work, but that is also a possibility to investigate.
>
>
>
> *From:* spacewalk-list-bounces at redhat.com <
> spacewalk-list-bounces at redhat.com> *On Behalf Of *Guy Matz
> *Sent:* Tuesday, June 11, 2019 4:21 PM
> *To:* Spacewalk-list at redhat.com
> *Subject:* [Spacewalk-list] Best Practice for adding a child Channel?
>
>
>
> Hi!  Is there a best way to add child channels?  I've added a channel, and
> made it a child channel in the "Activation Keys" section of the UI, but the
> channel does not show up on the client unless I add the child channel to
> the system.  Is there a better way?  Am I missing something?
>
>
>
> Thanks a lot,
>
> Guy
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20190611/089b043b/attachment.htm>