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 n
If you add the channel to the activation key *after* the client has been
registered with that key, nothing will be done on the client.
That's by design. New clients *will* get the child channel when registering
with that key.
If you need to modify many clients now, use the SSM.
Robert
sent
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
wrote:
> Hello,
>
>
>
> If the child channel is already associated with the activation key at the
> time of cl
] Best Practice for adding a child Channel?
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
mailto:william.hong...@marist.edu>> wrote:
Hello,
I
cewalk repo for your distribution. Hope this helps.
>
>
>
> *From:* spacewalk-list-boun...@redhat.com <
> spacewalk-list-boun...@redhat.com> *On Behalf Of *Guy Matz
> *Sent:* Tuesday, June 11, 2019 4:43 PM
> *To:* spacewalk-list@redhat.com
> *Subject:* Re: [Spacewalk-list] B
quite extensive.
From: spacewalk-list-boun...@redhat.com On
Behalf Of Guy Matz
Sent: Saturday, June 15, 2019 12:48 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] Best Practice for adding a child Channel?
Thanks. Would be nice if SSM could be managed from spacecmd . . .
On Tue
