Hide Forgot
Description of problem: In rhn-upgrade documentation is step 3 (execute /usr/bin/update-packages ) during satellite shutdown. And this process take a lot of time (several hours - I usually run it over night). We should do something about it: It seems to me that we can run it on running satellite. Either before or after upgrade (we have to verifify) Or we can prepare directory structure and hardlink old files to new one. And during satellite outage "only" update database to new path. And after upgrade of satellite (i.e when it is up and running) delete old files. Or something like that. Version-Release number of selected component (if applicable): # rpm -qf /usr/bin/update-packages spacewalk-backend-tools-0.5.28-34.el5sat
There's no way you could safely do any preparations like the one you described above (some hard linking of old files to new ones) on a running satellite. Conversion of filer is one of required steps for a valid upgrade to 5.3.0 and as such needs to be done as a part of the whole upgrade procedure. Introducing any pre- or post-steps is politically and technically unacceptable.