Description of problem: Installation takes much longer than a normal kickstart. Version-Release number of selected component (if applicable): How reproducible: Everytime. Steps to Reproduce: 1. Run a kickstart install without overriding the url Actual results: Install takes ages, especially grabbing the headers of the packages while it's preparing to install. This leads to a very long period before any package has actually been installed. With a large install this pre-install step can take an hour! Expected results: Install should be as snappy as if I wasn't using spacewalk. Additional info: This appears to be because all the rpm requests go through a wrapper, so requests go to (for example): /ty/3K7BjfcP/CentOS/tmpwatch-2.9.7-1.1.el5.1.x86_64.rpm If I just make available the dvd image that I'd pushed with make-ks-tree.sh directly on the webserver, and point the spacewalk install to it (using the url kickstart parameter) these accesses are no longer wrapped, and the install is *much* faster, and also puts noticeably less load on the server. If these calls are to be wrapped, they'd better be done so efficiently.
Changing Component from Installation (which is really meant to cover installation of the Spacewalk Server) to Server.
changed summary to mention kickstart which is different than spacewalk installation.
*** Bug 472595 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 472595 ***
I actually was doing all the work in 472595 so I'm closing this one out.