[Spacewalk-list] Kickstart and rhn-actions-control

[Josh Preston]

Hey guys,

 

Just a quick question:

 

When and/or where is the appropriate place to call rhn-actions-control
during a kickstart / activation? (or similar mechanisms)

 

I have the kickstart profile being just the base OS install; during
kickstarting, the machine is assigned the correct activation key that
updates channel memberships and adds packages as required.  I also have
the Config File Deployment option checked and have selected the
appropriate configuration channels.  Upon installation however, no
config files are deployed.  When looking in spacewalk, I can see the
install action is created properly but fails (in spacewalk) because of
the rhn-actions-control settings are not kosher.

 

During troubleshooting, I can simply reschedule the failed config deploy
action, then on the server perform the rhn-actions-control --enable-all
command followed by an rhn_check and viola!  Pay dirt.

 

Ideally, this is performed during kickstarting/installation -- I'm
assuming that I need to place an rhn-actions-control --enable-all
somewhere, just not sure the ideal spot to place it.  Can I just put it
in a post script?  My kickstart profile does not specify the "Tools"
channel, instead it is a subscription added by the activation key.

 

Please advise.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20120130/0232c860/attachment.htm>