Novell Home

My Favorites

Close

Please to see your favorites.

How to update to SLES/SLED 10 SP2

This document (7000387) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 10 (SLES10)
SUSE Linux Enterprise Server 9 (SLES9)
SUSE Linux Enterprise Server 8 (SLES8)
SUSE Linux Enterprise Desktop 10 (SLED10)
Novell Linux Desktop 9 (NLD9)

Situation

A system running one of the product versions listed above should be updated to SLES10 Service Pack 2 or SLED10 Service Pack 2.


Resolution

Like SLE 10 Service Pack 1, Service Pack 2 is a full product; a variety of methods for updating a system exist.

Don't panic:  This document is quite long and detailed, but don't be afraid. In fact the update procedure is very simple, straight-forward and (in most cases) self-explaining. Just pick the method that suits your needs best and start with it.

Important note:  After completing any form of update, look at the contents of the file /var/adm/rpmconfigcheck. This file contains a list of configuration files that could not be updated automatically. These files must be checked and the configurations adjusted manually.

Updating OES2

You can find detailed instructions on how to upgrade an OES system in the OES2 SP1 product documentation under http://www.novell.com/documentation/oes2/inst_oes_lx/data/bujr8yu.html.

Procedure for updating from SLES 8

There is no supported direct upgrade path from SLES8. To update a SLES8 installation, first update to SLES9. Refer to the SLES9 documentation for details.

Procedure for updating from SLES 9

The only way to update a SLES 9 system (SLES9 version GA, SP3 and SP4) can be done by booting from a SLE 10 SP2 media. See the respective section below.

Procedure for updating from NLD 9

The only way to update an NLD 9 system can be done by updating to NLD9 SP4 first, followed by updating to SLED 10 SP2 by booting from the SLE 10 SP2 installation media. This is the only way it has been tested.

Procedure for updating from SLES 10 and SLED 10

There is no supported direct migration path from SLES/SLED 10 GA to Service Pack 2. You have to perform an update to Service Pack 1 first. This is the only way it has been tested. The recommended way to update a GA system to SP2 level is by using the SP1 boot media to update to SP1 followed by using the SP2 boot media to update to SP2.

Procedure for updating from SLES 10 Service Pack 1 and SLED 10 Service Pack 1

There are different supported ways for updating a SuSE Linux Enterprise 10 SP1 system to SP2. You can either update to SP2 by using the online update tools to download patches or update using an SP2 installation media.

For installing SP2 by downloading patches, the following tools are supported:

  • 1) YaST Online Update (YOU)
  • 2) zen-updater
  • 3) rug
Alternatively, you can download the full SP2 media (CD or DVD ISO image) and use one of the following procedures, especially in case of environments without network access:
  • 4) by booting from SLES/SLED 10 SP2 media
  • 5) by using "Patch CD update"

Update to SP2 using patches

Attention:The update process has to be done completely from beginning to reboot. There is no automatic way to revert changes. Furthermore, the server has to be connected online during the whole update process. Prerequisites: You have to make sure to have your system registered. If you have not done this already, you can either do so by using the "Novell Customer Center Configuration" module in YaST or use the suse_register commandline tool. This will add an update source to your system.

1) Update by using YaST Online Update

  • Start the Online-Update module (YOU) from the YaST control center.
  • Press 'Accept' to apply updates with 'package management' flag set. Among others, this will install SLE 10 SP2 maintenance stack updates (Patch 'slesp1-libzypp' / 'sledp1-libzypp'). After installing those, YOU will restart itself.
  • Press 'Accept' to apply all available updates that are available for SP1. This may also install a new kernel, so you should reboot the system after applying this one.
  • Start the Online-Update module from the YaST control center again.
  • Select the optional "Update to SUSE Linux Enterprise Server/Desktop Service Pack 2" ('move-to-sles10-sp2' / 'move-to-sled10-sp2') patch. Do not select any other patch at the same time - except for for additional migration patches for add-on products. If an add-on product (e.g. the SDK) is installed, the respective migration patch will be selected automatically. The migration of the add-on product should be done at the same time as the base product, otherwise there would be rpm dependency conflicts.
  • After the patch is installed, YOU will close.
  • Start the Online-Update module from the YaST control center again.
  • Amongst others patches, 'slesp2o-sp2_online' and 'product-sles10-sp2' (or 'sledp2o-sp2_online' and 'product-sled10-sp2' accordingly) are preselected. Apply these patches to bring the system to SP2 level.
  • Reboot the system.

2) Update by using zen-updater

  • Start zen-updater from the system tray.
  • Apply updates with 'package management' flag ('slesp1-libzypp' / 'sledp1-libzypp', amongst others).
  • At this point, an 'rczmd restart' and a restart of the zen-updater application might be necessary.
  • Apply all maintenance updates that are available up to this point. This may also install a new kernel (a subsequent reboot is recommended).
  • Select the 'move-to-sles10-sp2' patch (or 'move-to-sled10-sp2'  accordingly). If add-on products are installed, migration patches for these will be selected automatically.
  • Select "Refresh" from the zen-updater context menu.
  • After that, amongst other patches 'slesp2o-sp2_online' and 'product-sles10-sp2' (or 'sledp2o-sp2_online' and 'product-sled10-sp2' accordingly) are preselected in zen-updater. Apply these patches to bring the system to SP2 level.
  • Reboot the system.

3) Update by using rug

  • Open a root shell.
  • It is recommended to quit zen-updater. Do not only close it's window! If unsure, run 'killall zen-updater'.
  • Run 'rug in -t patch slesp1-libzypp' (or 'rug in -t patch sledp1-libzypp' accordingly). This will update the maintenance stack.
  • Run 'sleep 40 && rug ping -a' to wait for the ZMD to wake up after it's restart.
  • Run 'rug in -t patch move-to-sles10-sp2' (or 'rug in -t patch move-to-sled10-sp2' accordingly).
  • Run 'rug refresh && rug ping -a'.
  • Run 'rug up -t patch' to update more packages with 'packagemanagement flag' set.
  • Run 'sleep 240 && rug ping -a' in order to wait for ZMD to become responsive again.
  • Run 'rug up -t patch' again.
  • Reboot the system.

  • The following script can be used as a base for a complete unattended update from SP1 to SP2:

    #!/bin/bash
    set -x
    rug in -y -t patch slesp1-libzypp          # For SLED use sledp1-libzypp
    sleep 40 && rug ping -a
    rug in -y -t patch move-to-sles10-sp2 # For SLED use move-to-sled10-sp2
    rug refresh && rug ping -a
    rug up -y -t patch
    sleep 240 && rug ping -a
    rug up -y --agree-to-third-party-licences  -t patch <<EOF
    n                                                          # For an automatic reboot after the migration, you may change 'n' to 'y'
    EOF

Technical background

As a general technical background, these are the steps involved when updating by using YaST online update, zen-updater, or rug.
  • The packagemanagement software itself is updated first (patches slesp1-libzypp, slesp1-yast2-installation, and slesp1-yast2-online-update / on SLED: sledp1-libzypp, sledp1-yast2-installation, and sledp1-yast2-online-update).
  • The patch to enable migration to SP2 needs to be applied explicitly. This patch is called 'move-to-sles10-sp2' or 'move-to-sle s10-sp2', depending on the product. It is an optional patch and therefore it is not preselected.
  • The patch installs the SP2-migration product marker.
  • A log of the operation of this patch is kept as  /var/log/YaST2/move-to-sles10-sp2-script.log.
  • Furtheron 'suse_register' is called to add theSLES10-SP2-Online or SLED10-SP2-Online catalog. Additionally for SLED, third-party vendor packages (ATI, NVIDIA, ...) are added.
  • At this point, the installation source may need to be adapted if add-on products, repositories of other vendors or other third party repositories were configured.
  • The online tools now offer two patches to move the system to SP2:
  • The 'slesp2o-sp2_online'/'sledp2o-sp2_online' is a meta patch which contains all packages to bring the system to SP2 level.
  • The 'product-sles10-sp2' ('product-sled10-sp2' on SLED respectively) replaces the SP2-migration product marker with the SP2 product marker. It furtheron calls 'suse_register' again to unsubscribe the SLES10-SP1-Online or SLED10-SP1-Online catalog and to add the SLES10-SP2-Update or SLED10-SP2-Update catalog.
  • A log of the operation of this patch is stored as /var/log/YaST2/product-sles10-sp2-script.log.
  • As a result, there are now three channels listed:
    • The SLE 10 SP1 installation source
    • The SLES10-SP2-Online/SLED10-SP2-Online catalog, which contains the software which was necessary to perform the actual update to SP2.
    • The SLES10-SP2-Updates/SLED10-SP2-Updates catalog, which contains software updates published after the release of SP2.
Both, the SLE 10 SP1 catalog and the SP2-Online catalog now act as the installation source.
If the system has been updated from a SLE 10 GA version previously, additionally the SLES10-SP1-Online/SLED10-SP1-Online catalog exists.

In order to simplify this setup you can substitute certain catalogs by the SLES10-SP2-Pool/SLED10-SP2-Pool catalog. SP2-Pool is a rpm-md repository containing all packages from the SP2 media (It does not contain the patches for migration). By default, the catalog is returned as unsubscribed and not added to YaST.

So, when the system is on SP2 level, one possible setup is to remove the SLE 10 GA / SLE10 SP1 installation source catalog, the SP1-Online and the SP2-Online catalogs and to use the SLES10-SP2-Pool / SLED10-SP2-Pool catalog instead. Note not to remove the SP2-Updates catalog!

The document Which software catalogs to mirror with Subscription Management Tool explains the different catalogs and which ones that are needed in the various scenarios of installation sources and update paths in more detail.

Update to SP2 using patches by using Subscription Management Tool for SUSE Linux Enterprise

As an alternative to downloading the updates for each single client system from the Novell update server, it is possible to use Subscription Management Tool for SUSE Linux Enterprise to mirror the updates to a local server.
This tool acts as Novell Customer Center proxy both for client registrations and as software update repository. It runs on a SLES 10 SP2 server and the Novell Appnote Keep your SUSE Linux Desktops, Servers and OES Servers Updated with Subscription Management Tool for SUSE Linux Enterprise gives an overview of its features as well as instructions on how to implement it.

Update using an SP2 installation media

Please obtain the ISO images from http://download.suse.com.

4) Update by booting from a SLES/SLED 10 SP2 media

To start the standard update from CD-ROM or DVD, reboot your computer with this medium in your CD-ROM or DVD drive. Perform a system update instead of a fresh installation. To achive this, select "Installation" -> Select the language -> Agree to the License Agreement ->  Select "Update" instead of "New Installation".

4.1) Providing the SP2 media as a network installation source

It is also possible to provide the installation media via network. SLE 10 Service-Pack 2 is a complete product. So it can be added to an Installation Server in the same way as every other SUSE LINUX Enterprise Product.

The procedure on how to setup an installation server and to add the service pack is described in the Installation Notes for SUSE Linux Enterprise Server/Desktop 10 SP2. You will find this document in the file README on the first DVD. For SLES see chapter "3.1 Setting Up an Installation Server" of this document. For SLED, see chapter 6.2 of the README.

You will find a more detailled guide in the documentation of your SLES9/SLES10 GA version. For SLES10 have a look at chapter 4.2.1 "Setting Up an Installation Server Using YaST" in the file sles-admin.pdf, which you can find on the first CD/DVD in the directory /docu/en. This document is also available online under http://www.novell.com/documentation/sles10/. For SLES9 you find this chapter in the file docu/en/manual.pdf (online available under http://www.novell.com/documentation/sles9/).

4.1.1) To start the update, go ahead as follows:
  • You need a bootable medium to initialize the process. Booting via network/PXE is also possible. For ready-to-apply configuration examples for PXE boot, see chapter 4.3 in the SLES10 documentation mentioned above (online available at http://www.novell.com/documentation/sles10/).
  • Boot the machine and choose "Installation".
  • If your installation source is announced via SLP, enter "install=slp" in the "Boot Options" field (or change the installation source via "F3", if this is available on your platform).
  • After the machine boots, it shows a selection of install options it has found via SLP.
  • If SLP is not configured on your installation server, you have to enter the IP and path to your installation source to the "Boot Options" field manually. If the installation source is configured as NFS share see the following example:
    install=nfs://IP_ADDRESS_OF_YOUR_SERVER/PATH_TO_SP2
    For other server types see the documentation mentioned above.
  • Select "System Update" instead of performing a fresh installation.
  • For an alternative solution see TID 7001502 ("Yast2 online update from SLES10 SP1 to SP2 via NFS fails").

4.2) Providing the SP2 media as a network installation source for YaST Online Update (only supported for SLES, not for SLED)

It is also possible to provide the installation media in a way that you can use YaST Online Update for updating. The advantage is, that you don't have to boot from an Installation media. Instead you update from a running system. This minimizes downtime. (The procedure is also described in  chapter 5.4 of the SLES README mentioned above). Please note: This procedure is not supported for SLES 10 version GA. Your system has to be on SP1 level in order to use this method.

You have to create an installation source as described in the chapter above. After this, you have to do an additional  modification.  Go into the directory named "patches"  and create a symlink to "../suse":

ln -s ../suse .
4.2.1) To start the update, go ahead as follows:

  • Add the new repository. In case you have released the repository as an NFS share, go ahead as follows:
    • You first have to mount the installation share manually, e.g. under /mnt.
    • Start YaST2, select "Software" -> "Change Source of Installation Source".
    • Disable the SLES10 SP1 source and SLES10-SP1 update channel.
    • Add the new repository by selecting "Add" -> "Local Directory". Important: You have to specifiy the path to the patches subdirectory (in this case /mnt/patches), otherwise YaST Online Update will not work.
    • Update the system by starting "YaST" ->"Online Update".
  • The procedure for FTP and HTTP repositories are similar:
    • Disable the SLES10 SP1 source and SLES10-SP1 update channel in the YaST Installation Source Menu, as describe above.
    • Add the new repository by selecting "Add" -> "HTTP" or"FTP", depending on your installation server configuration. Again, you have to specifiy the path to the patches subdirectory, otherwise YaST Online Update would not work. The path would be for example::
      http://server/instsource/SLES10-SP2-i586/patches
    • Update the system by starting "YaST" ->"Online Update".

5) Update by using "Patch CD update" (supported only for SLES, not for SLED!)

A physical CD/DVD drive is required to use this update method. On systems without CD/DVD drives (e.g. System z) please use a different update method.

The procedure is described in the Installation Notes for SUSE Linux Enterprise Server 10 SP2. You will find this document in the file README on the first CD. In here, see chapter 5.3.

Please note: The update process should not be executed by using a remote connection, e.g. ssh. The reason is the following: while YaST installs the the update packages the network connection is interrupted for a short time. Therefore YaST would be interrrupted.

Also note, that due to a bug in YaST the new SP2 installation- and update sources are not refreshed. For a solution see TID 7000493.

Status

Top Issue

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7000387
  • Creation Date:15-MAY-08
  • Modified Date:05-MAY-14
    • SUSESubscription Management Tool
      SUSE Linux Enterprise Desktop
      SUSE Linux Enterprise Server
      SUSE Linux Enterprise Software Development Kit

Did this document solve your problem? Provide Feedback