Hi Chris:
So if you don't want these files present for certain systems/profiles, you'll need to modify the appropriate
kickstart
scripts accordingly as you are already doing.
That makes sense. Thanks for the explanation.
What I don't understand is why these files would be causing issues
during
your kickstart script. None of my installations at $WORK start on a network that can get out to the internet and yet they work fine. Are
you
using yum in the post-install script?
That is very interesting. When I log into the machine, I cannot update any packages if those files (CentOS-*.repo) are present. But when I run 'yum grouplist' it shows that the packages did install correctly. That supports your argument.
I am not using yum directly in the post-install script. I am only using the %packages section in anaconda to get the 'Virtualization' group and the 'koan' package.
I don't have much experience with cobbler so it is very likely that I am doing something bone-headed. Can you suggest some ideas for debugging? I am already scanning through the logs in /root/ and in /var/log/ but I must be missing something.
Cheers,
Joe
-----Original Message----- From: Chris Ess [mailto:caess@ithiriel.com] Sent: Saturday, January 01, 2011 11:02 PM To: cobbler mailing list Cc: Joe Linoff Subject: Re: cobbler PXE boot problem -- can't get rid of /etc/yum.repos.d/CentOS*.repo Importance: Low
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On Sun, 2 Jan 2011, Scott Henson wrote:
On Sat, 1 Jan 2011 21:31:27 -0800, "Joe Linoff" jlinoff@tabula.com
wrote:
I am currently experimenting with removing those files in the
kickstart
but I was hoping that there was a more elegant solution. I would
like to
tell cobbler not to install the default CentOS-Base.repo and CentOS-Media.repo for a specific system or profile.
I'm pretty sure anaconda is dropping those file in place. Having anaconda not drop those files would be a question for anaconda or the CentOS devs.
It looks like these files are being added by the centos-release package:
$ sudo rpm -qf /etc/yum.repos.d/CentOS-Base.repo centos-release-5-5.el5.centos
However, given the list of files in the centos-release package, I don't recommend removing it. So if you don't want these files present for certain systems/profiles, you'll need to modify the appropriate kickstart scripts accordingly as you are already doing.
What I don't understand is why these files would be causing issues during your kickstart script. None of my installations at $WORK start on a network that can get out to the internet and yet they work fine. Are you using yum in the post-install script?
Sincerely,
Chris Ess System Administrator / CDTT (Certified Duct Tape Technician)