Our spacewalk server is now working quite well.
Before rollout I tested the update of our Scientific Linux 6 channel
from 6.0 to 6.1 (6.1 is called 6rolling, because it is not release yet).
New kickstarted clients work well, 6.0 clients can update, but after the
update to 6.1 you cannot install
Scott Rakow wrote:
Did you create a Distribution on your Spacewalk server and relate it to your
profile? I believe that is how Spacewalk/Cobbler knows where to pull the
RPM's from.
Yes. Kickstarting works. Well, the first part works:
It installs the base system from the distribution image and
I found the issue:
Sascha Frey wrote:
The HTTPd logs on the server show a bad request (400):
129.70.137.XX - - [24/Jun/2011:15:57:50 +0200] POST /XMLRPC HTTP/1.1 200 1544
129.70.137.XX - - [24/Jun/2011:15:57:50 +0200] GET
/XMLRPC/GET-REQ/sl-x86_64-6/repodata/repomd.xml HTTP/1.1 400 309
Hi,
we just set up a spacewalk server and got our first client kickstarted.
The client cannot access any channel on the spacewalk server.
'yum update' returns 'Error: Cannot retrieve repository metadata
(repomd.xml) for repository: sl-x86_64-6. Please verfiy its path and try
again'.
It does
