7.9 Using SUSE Manager to Patch an OES Server

SUSE Manager is a server solution for providing updates, patches, and security fixes for single SUSE Linux Enterprise, OES, and Red Hat Enterprise Linux clients. It comes with a set of tools and a Web-based user interface for management tasks. For more information on SUSE Manager, see the SUSE Manager documentation.


  • Novell Archive and Version Services installation is not supported on an OES server that has been patched using SUSE Manager.

  • SUSE Manager-based patching support is available only from OES 11 onwards.

You can use SUSE Manager to patch an OES 11, OES 11 SP1 or OES 11 SP2 server.

7.9.1 Setting Up SUSE Manager

Use the information contained in the following sections to set up a SUSE Manager server:

Installing SUSE Manager

For more information about installing, patching and mirroring, see the SUSE Manager 1.7 Quick Start.

  1. Install SUSE Manager.

  2. Patch SUSE Manager before configuring it.

  3. When you configure SUSE Manager, provide the appropriate mirror credentials for access to the OES and SLES channels.

Mirroring the Required OES and SLES Channels

  1. Use PuTTY to log in to SUSE Manager with administrative credentials.

  2. Execute the mgr-ncc-sync -l command to view all channels that you are allowed to synchronize with SUSE Manager.

    The output lists both parent and child channels. The following notations are used to mark each channel:

    • [.] Denotes a channel that is not mirrored or synchronized.

    • [p] Denotes a channel that was previously mirrored or synchronized.

  3. Select the channels you want to import.

    You can import child channels only if their respective parent channels are already imported.

    IMPORTANT: After they are mirrored, SUSE channels cannot be deleted. Only custom software channels can be deleted.

  4. For each channel that you want to mirror, run the mgr-ncc-sync -c <the channel name> command.

    For example, to mirror oes11sp1-pool-x86_64, the command is:

    mgr-ncc-sync -c oes11sp1-pool-x86_64

    The channel data is imported into the SUSE Manager database and a full synchronization is triggered for that channel.

  5. (Conditional) If this is the first time the OES channel has been mirrored, you see the following error message:

    ChannelException: The GPG keys listed for the oes11sp1-pool-x86_64 repository are already installed but they are not correct. Check that the correct key URLs are configured for this repository.

    Use the following steps to resolve the issue:

    1. Run the spacewalk-repo-sync -c <any-oes-channel-name> command.

      For example, spacewalk-repo-sync -c oes11-pool-x86_64.

    2. When you are prompted to import the keys, import the keys and continue with Step 6.

      After the keys are imported, other OES channels are mirrored without any issues.

  6. Repeat Step 4 and mirror the following OES 11 SP1,OES 11 SP2, SLES 11 SP1, SLES 11 SP2 and SLES 11 SP3 channels:

    • For OES 11: sles11-sp1-pool , sles11-sp1-updates, sles11-sp1-suse-manager-tools, oes11-pool, oes11-updates, and sles11-extras.

    • For OES 11 SP1: sles11-sp2-core, sles11-sp2-updates, sles11-sp2-suse-manager-tools, sles11-sp2-extension-store, oes11-sp1-pool, and oes11-sp1-updates.

    • For OES 11 SP2: sles11-sp3-pool, sles11-sp3-updates, sles11-sp2-suse-manager-tools x86_64 SP3, oes11-sp2-pool, and oes11-sp2-updates.

Creating the Activation Keys and the Bootstrap File

To create and subscribe channels with the activation keys that can be used to register the OES servers with SUSE Manager:

  1. Log in to the SUSE Manager Web console with administrative credentials.

  2. Click Systems > Activation Keys > + create new key, specify the following details, then click Create Activation Key.

    • Description: Specify a short description that identifies the settings this key creates on the systems that use it.

    • Key: Specify a key of your choice. For example, novell-production could be a key.

    • Usage: Specify the number of servers that can use this key. Leave it blank for unlimited usage.

    • Base Channels: Select SUSE Manager Default.

    • Add-On Entitlements: Select Monitoring and Provisioning.

  3. Click Packages tab, enter rhncfg-actions in the input field, then click Update Activation Key.

  4. Click Child Channels, deselect all the selected channels by holding the Ctrl key, then click Update Key.

Creating the OES Bootstrap Script and Registering the OES Server with SUSE Manager

A bootstrap file is used to register the OES server to SUSE Manager. For more information on bootstrap scripts, refer to the SUSE Manager 1.7 Quick Start.

  1. Create an OES bootstrap file and add an activation key:

    1. Use PuTTY to log in to SUSE Manager with administrative credentials.

    2. Navigate to /srv/www/htdocs/pub/bootstrap.

    3. Create a copy of the bootstrap file using the cp bootstrap.sh oes11strap.sh command.

    4. Use an editor to open oes11strap.sh, locate the following elements, and add the following:

    5. Identify the following block and remove exit 1.

      echo "the exit below)"
      exit 1
    6. Save and exit the oes11strap.sh file.

  2. Register the OES servers to the SUSE manager for patching and upgrading:

    1. Use PuTTY to log in to the OES server with administrative credentials.

    2. Execute the curl -Sks https://<SUSE Manager Server_Hostname OR IP_Address>/pub/bootstrap/oes11strap.sh | /bin/bash command.

7.9.2 Patching an OES 11 or Later Server Using SUSE Manager

  1. Ensure that you have completed Setting Up SUSE Manager.

  2. Log in to the SUSE Manager Web console (https://<SUSE Manager Server_hostname or IP_address>) with administrative credentials.

  3. Click Systems.

    SUSE Manager lists all the registered OES servers along with the number of patches available for each OES server.

  4. Select the OES server, click Software > Software Channels, then verify that the required channels are selected.

  5. To apply a patch, select the OES server, click Software > Patches, select all the patches, then click Apply patches > Schedule the patch > Confirm.

  6. After all the patches are applied, click Systems, select the OES System to be patched and then click Software > Packages > Upgrade.

  7. Select all the packages, then click Upgrade Packages > Confirm.

    The OES server is updated with all the patches, according to the schedule.