Bug 87649 - Upgrade OS onto different disks on a live system
Summary: Upgrade OS onto different disks on a live system
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: anaconda   
(Show other bugs)
Version: 2.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords: FutureFeature
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-03-31 21:19 UTC by Dave Dulek
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-03-31 21:20:53 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Dave Dulek 2003-03-31 21:19:00 UTC
We would like the ability to install patches and version upgrades in a stand aside 
mode.  This would need to happen on the "live" system. 
 
Basically, this install would copy the existing "root" file systems (i.e /, /usr, /var) 
onto the "new" disk.  Upgrades and patches would be then applied to the "new" 
filesystems.  A reboot would then be required to boot off the "new" system file 
systems.  If problems arise you can then boot the "old" system and revert back to 
the system prior to the changes. 
 
This would be similar to the "Live Upgrade" of Sun Microsystem's Solaris.

Comment 1 Michael Fulbright 2003-03-31 21:20:53 UTC
We do not plan to support this mode of upgrades in the near future.

If you wanted to do this you could put code in your %pre of a kickstart file to
backup the filesystems, upgrade the existing, and if you don't like what
happened copy the backup over the upgraded system.




Note You need to log in before you can comment on or make changes to this bug.