[Spacewalk-list] spacewalk 1.3 - python-ethtool package being a problem within kickstart.

[Matthew Darcy]

For the sake of argument,

I've upgraded the spacewalk server to 1.4 and the problem still persists.

To test this a little further, I build a base machine from the same kickstart profile (removed the python-ethtool package from the install list).
Went to the spacewalk URL for the python-ethtool package, downloaded it, and installed it with rpm and it installed fine, so there is no problem with the package, or the fact that it's hosted, there is something wrong when the kickstart process trys to get the package from the repo, it can't see it.

I am genuinely %101 stumped as to why this could be.

Matt


From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Matthew Darcy
Sent: 18 May 2011 13:51
To: spacewalk-list at redhat.com
Subject: [Spacewalk-list] spacewalk 1.3 - python-ethtool package being a problem within kickstart.

Centos 5.6 x86_64 hosting a Spacwalk 1.3 Oracle XE environment.

I've built a parent channel for Centos 5 with 3 child channels.

1.) Centos 5 updates
2.) Spacewalk clients
3.) EPEL (needed for python-ethtool for spacewalk registration)


My kickstart profile is for a test VM, it should build a simple VM install the spacewalk client tools from the spacewalk client child repos and the python-ethtool package from the EPEL child repo to allow the server to register its self with the spacewalk server.

A kind user on the #spacewalk IRC explained I needed the EPEL repo for python-ethtool as without this the client can't register with the spacewalk server.

I've added the EPEL repo and told the kickstart profile to install python-ethtool

When the kickstart build starts, it goes throught he basics, boots, lays out the file system and then starts working out the packages,  it complains that I have specific a package "python-ethtool" that doesn't not exist abort continue (see screen shot 1)

However....

the EPEL repo does contain the python-ethtool package, and if I hit the download button on it, it does download the package. (see screen shot 2)

If I check the kickstart backgroun tty's I also see the epel repo being added fine (see screen shot 3)

I've attatched the kickstart file to show how the build should work,

I have no idea why this package is not showing up as available and would appreciate any suggestions.

The EPEL repo has been synced down from http://mirror.bytemark.co.uk/fedora/epel/5/x86_64/ and does not complain of errors.

Thanks,

Matt







______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20110519/63fbfaab/attachment.htm>