How do I add local repos on Spacewalk kickstarted systems?
 

I'm trying to configure Spacewalk so that the local repos I've sync'd will be available in the OS after the system is kickstarted. I've created a base channel for the OS install repo that has several child channels which have different repos per channel (EPEL, Spacewalk client, etc). After a system is kicked I cannot see these repos in /etc/yum.repos.d

The kickstart profile lists the child channels in the "Operating System" tab and they are also selected in the Activation Key's Child Channels tab.

There is an error in the ks-rhn-post.log where the client registration is failing:
I'm not sure why these repos are not being seen... how can I add them?

Are you running Red Hat 6 or 7?

http://www.cyberciti.biz/tips/rhel5-...epository.html
http://www.linuxquestions.org/questi...to-yum-882734/

I'm running CentOS 6. Based on the urls you provided I think you slightly miss-understand my question. I have local repos in spacewalk I want to be available as part of a kickstart from spacewalk. In other words they should automatically be there and the kicstart post config is erroring because they are not. Right now only the base repo is showing up.

Hi:

Sorry I misunderstood.

I looked up the error:
Here are 2 threads related to your error that I could find.
http://blog.gmane.org/gmane.linux.re...month=20120201
https://www.redhat.com/archives/spac.../msg00070.html

You said that "they" should be there; do you mean a config script or a repository?

If your proxy is connected to a spacewalk server I won't be much help; sorry.
I don't have server experience, I'm still learning that:-

Thanks for your help - I am new to spacewalk so I am learning this too. It looks like the systems repos listed in /etc/yum.reopsd are actually not used. I'm not 100% sure on this but I kickstarted a new server and then manually added it to spacewalk. Once in spacewalk I can pick packages to install from the gui - for instance osad which is client that allows remote commands / scripts to be run from spacewalk.

In any event I'm still not sure why my systems are failing to automatically register with spacewalk however... that is my main problem at this point.

Your Welcome.

I don't get why your systems are failing to register with spacewalk.

Maybe double check that Spacewalk is configured correctly. Spacewalk could be dependent upon other libraries and if they are not installed that could be a problem too. Communication between system and Spacewalk could be misconfigured but I'm not sure where. It could be as simple as a configuration file needing a string added or taken away.
I'll learn what I can about Spacewalk and how to set it up.

If I find anything I'll post it for you.

Well - I found out that there was a few things that were causing the issue for me. The first seems to be that the activation key I was using with my kickstart did not have all the repos assigned to it and thus could not pull in the packages needed to register itself with spacwealk - but it had the base system and finished kickstarting fine so it was hard to discern what was going on. The second was I did not have the spacewalk package group in the kickstart config, nor pyhton-hwdata which was the final fail for me. Once those were added I get an automatically added system to spacewalk after it's kicked :)

Glad to hear you found out what the problem was.

Is Spacewalk working now?