Bug 523395

Summary:	/usr/bin/update-packages takes long time and can be done after or before satellite outage
Product:	Red Hat Satellite 5	Reporter:	Miroslav Suchý <msuchy>
Component:	Upgrades	Assignee:	Milan Zázrivec <mzazrivec>
Status:	CLOSED WONTFIX	QA Contact:	Brandon Perkins <bperkins>
Severity:	medium	Docs Contact:
Priority:	low
Version:	530	CC:	cperry
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-10-26 14:13:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Miroslav Suchý 2009-09-15 10:32:48 UTC

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

Comment 1 Milan Zázrivec 2009-10-26 14:13:41 UTC

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.