Novell Home

My Favorites

Close

Please to see your favorites.

How to update to SLES/SLED 10 SP1

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

Environment


Novell SUSE Linux Enterprise Server 10
Novell SUSE Linux Enterprise Server 9
Novell SUSE Linux Enterprise Desktop 10
Novell Linux Desktop 9

Situation

You want to update one of the product versions mentioned above to SLES/SLED 10 Service Pack 1.

Resolution

Opposite to previous SLE 9 service packs, SLE 10 SP1 is a full product. Therefore a variety of methods for updating a system exist.

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.

Procedure for updating SLES 9

The only way to update a SLES 9 system can be done by booting from a SLE 10 SP1 media. See the respective section below.

Procedure for updating NLD 9

Upgrade to SLED10-GA first and then update to SP1. This is the only way it has been tested.

Procedure for updating SLES 10 and SLED 10

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

For installing SP1 via downloading patches, the following tools are supported:

  • 1) YaST Online Update (YOU)
  • 2) zen-updater
  • 3) rug
Alternatively, you can download the full SP1 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 SP1 media
  • 5) by using "Patch CD update"

Update to SP1 via 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. Also, it is recommended to make sure, that all updates are installed that are available up to this point. However this is not mandatory.

1) Update by using YaST Online Update

  • Start Online-Update module from YaST control center.
  • Select the optional "Update to SUSE Linux Enterprise Server/Desktop Service Pack 1" (move-to-sles10-sp1 / move-to-sled10-sp1) patch. Do not select any other patch at the same time.
  • Start Online-Update module from YaST control center.
  • Select now only the patch with the name "YOU update for YaST2". (It should be the only patch that is preselected).
  • Now update all other packages. After this, your system is on SP1 level.
  • Reboot.

2) Update by using zen-updater

  • Start zen-updater from the system tray.
  • Select the "move-to-sles10-sp1" patch. Do not select any other patch at the same time.
  • Press the "Update" button.
  • Wait for success message.
  • A small popup will appear informing about changing the update server to nu.novell.com.
  • Later, a popup asking to provide root password will appear.
  • After installing maintenance stack update, a window with patch selection will appear.
  • Select/unselect the required patches and press 'Accept'.
  • After the update has finished: reboot the system.

3) Update by using rug

  • (If you have opened zen-updater on your desktop, make sure to quit it before starting the update procedure with rug. Do not only close the zen-updater window. For details on the background see TID 3864473.)
  • Open a root shell
  • Run 'rug in -y -t patch switch-update-server'. Do not select any other patch at the same time.
  • Run '/usr/bin/switch-update-server'
  • Check that your update server is now nu.novell.com (call rug sl to find out)
  • Run 'rug sub SLES10-Updates' (or 'rug sub SLED10-Updates' accordingly)
  • Run 'rug in -y -t patch move-to-sles10-sp1' (or 'rug in -y -t patch move-to-sled10-sp1' accordingly)
  • Run 'rug refresh'
  • Run 'rug sub SLES10-SP1-Online' (or rug sub SLED10-SP1-Online accordingly)
  • Run 'rug in -y -t patch slesp1o-liby2util-devel' (or 'rug in -y -t patch sledp1o-liby2util-devel' accordingly)
  • Run 'rczmd restart'
  • Run 'rug up' (for unattended updates via script it is possible to use 'rug up -y --agree-to-third-party-licences')
  • Run 'rug in -y -t patch product-sles10-sp1' (or 'rug in -y -t patch product-sled10-sp1' accordingly) to install the update stack patch followed by
  • Reboot

Technical background

As a general technical background, these are the steps involved when updating by using YaST online update, zen-updater, or rug.
  • You have to install the patch to enable migration to SP1 manually. The patch is called 'move-to-sles10-sp1' or 'move-to-sle s10-sp1', depending on the product.
  • The patch installs two additional packages: the updated 'suseRegister' package and the 'switch-update-server package'.
  • Via 'switch-update-server' script, the update source is migrated from NU service 'update.novell.com' to NU service on'nu.novell.com'.
  • The SP1-Migration product is installed.
  • 'suse_register' is called to add the SLES10-SP1-Online/SLED10-SP1-Online catalog. Additionally for SLED, third-party vendor packages (ATI, NVIDIA, ...) are added. If the SDK (SuSE Development Kit) ist installed, appropriate catalogs for updating the SDK are added as well (SLE10-SDK-SP1-Online catalog). This ensures, that the SDK is updated to SP1 level also.
  • The online tools now offer a full set of patches to move the system to SP1.
  • By installing the patch-liby2util-devel-* patch, the package manager stack is updated first.
  • After that, all patches to install SP1 functional level are installed, including a new kernel and a patch which updates the product information to be SLES10-SP1-Online/SLED10-SP1-Online. The product patch is important for registration after reboot to succeed. The newly introduced packages in SP1 are delivered as optional patches.
  • You are asked to reboot the machine. This is not done automatically.
  • After reboot, the 'suse-register' script detects, that a new registration is needed and starts the registration on background. (However, if the host is using NetworkManager, the registration at boot time is skipped, and is triggered via NetworkManagerDispatcher.)
  • The registration can take quite some time. There is no visual feedback if it is finished or not, except for zen-updater turning orange if there are already maintenance updates waiting for this new SP1 installation.
  • During this process, the SLES10-SP1-Updates/SLED10-SP1-Updates channel is added.
  • As a result, there are now three channels subscribed:
    • The SLES10 GA installation source
    • The SLES10-SP1-Online/SLED10-SP1-Online channel, which contains the software which was necessary to perform the actual update to SP1
    • The SLES10-SP1-Updates/SLED10-SP1-Updates channel, which contains software updates published after the release of SP1.
Both, the SLES10 GA channel and the SLES10-SP1-Online/SLED10-SP1-Online channel now act as the installation source. Therefore neither of them must be removed.

Update to SP1 via patches by using a local update server

As an alternative to downloading the updates for each single client system from the Novell update server, it is possible to mirror package updates for SLE 10 from the Novell update service and make these updates accessible to local clients. The package which allows to setup a local mirror is called "yup" (Yum Update Proxy). A script which allows an unattentend update of a client to Service Pack 1 is included in the yup package as well.

You can find more information about the procedure and the support status in the following Technical Information Document:
http://www.novell.com/support/search.do?cmd=displayKC&docType=kc&externalId=3065146&sliceId=SAL_Public


Update via using an SP1 installation media

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

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

To start the standard update from CD-ROM or DVD, reboot your computer with this medium in your CD-ROM or DVD drive. Select "Installation" -> "System Update" instead of fresh installation.

4.1) Providing the SP1 media as a network installation source

It is also possible to provide the installation media via network. SLE 10 Service-Pack 1 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 SP1. You will find this document in the file README on the first CD. 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. For SLES9 you find this chapter in the file docu/en/manual.pdf.

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.
  • 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_SP1
    For other server types see the documentation mentioned above.
  • Select "System Update" instead of performing a fresh installation.

4.2) Providing the SP1 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).

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:
  • Mount the first media (for example at /mnt) and change to the"suse" directory below that directory (for example /mnt/suse).
  • Because the old YaST2 is not able to parse the repodata in the patches directory correctly you have to update the software stack manually by running the following rpm command:
    rpm -Uhv \
    */libzypp-2.15.*.rpm \
    */libzypp-zmd-backend-*.rpm \
    */liby2util-2.13.*.rpm \
    */yast2-core-2.13.*.rpm \
    */yast2-pkg-bindings-2.13.*.rpm \
    */yast2-perl-bindings-2.13.*.rpm \
    */yast2-qt-2.13.*.rpm \
    */yast2-2.13.*.rpm \
    noarch/yast2-online-update-*.rpm \
    */yast2-country-2.13.*.rpm \
    */yast2-ncurses-2.13.*.rpm \
    */yast2-packager-2.13.*.rpm \
    */yast2-slp-2.13.*.rpm \
    noarch/yast2-installation-2.13.*.rpm \
    noarch/yast2-inetd-2.13.*.rpm \
    */zmd-*.rpm \
    */zypper-*.rpm \
    */rug-*.rpm \
    noarch/suseRegister-1.*.rpm
  • Leave the suse directory and unmount the media.
  • Make sure zmd is running, if unsure, run "rczmd restart".
  • Make sure zmd has finished reading his database, run "rug sl" until there is no 'pending' status anymore.
  • 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 GA source and SLES10 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 GA source and SLES10 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-SP1-i586/patches
    • Update the system by starting "YaST" ->"Online Update".

5) Update by using "Patch CD update" (available 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 SP1. 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 via remote connection, e.g. via ssh. The reason is, while YaST installs the the update packages the network connection is interrupted for a short time, therefore YaST would be interrrupted.

Status

Top Issue

Bug Number

354431

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:3509359
  • Creation Date:04-FEB-08
  • Modified Date:30-APR-12
    • SUSESUSE Linux Enterprise Desktop
      SUSE Linux Enterprise Real Time Extension
      SUSE Linux Enterprise Server
      SUSE Linux Enterprise Software Development Kit

Did this document solve your problem? Provide Feedback