[Spacewalk-list] Provisioning, activation key and child channels

[Jonathan DeHaan]

In my experience, this is not the case. The activation key has no effect 
on the kickstart process until the post script section where the client 
is registered to Spacewalk. Only at that point does the client acquires 
access to the child channels defined in the activation key. If you put 
yum install commands into the post script, then you should be able to 
reference packages in the child channels associated with the activation 
key, because registration happens before your post script.

The hint on the 'Kickstart Details/Operating System' page is slightly 
misleading. The child channels on the kickstart page are only available 
during the kickstart process itself. They aren't available after install 
has completed, even if you have no activation key and don't register the 
client with Spacewalk.

Jonathan DeHaan
Linux Systems Engineer


On 02/16/2011 05:42 AM, Michael Gliwinski wrote:
> Hi All,
>
> Could someone verify something in Spacewalk 1.2/1.3 please?
>
> Assuming you have:
>
>   - an activation key A which has a base channel C and child channels C1, C2,
> ... associated
>   - a kickstart profile K which:
>     - has activation key A associated with it
>     - *does not* have any child channels selected on 'Kickstart
> Details/Operating System' page in kickstart wizard
>
> Could you check if the generated kickstart file has 'repo' lines generated for
> the child channels C1, C2, ...?
>
> I was sure this is what is supposed to happen and I'm almost sure this is what
> used to happen in Spacewalk 1.1, but now the only repo line in my kickstart is
> the one for VT repo (which shouldn't actually even be there as there's no such
> repo).  (BTW, the repo lines are generated if I select those child channels on
> 'Kickstart Details/Operating System' page but this same page says these will
> be ignored if used activation key has child channels associated).
>
> Many thanks,
> Michael
>
>