SUSE Manager/SLES 10 Betatest

From MicroFocusInternationalWiki
Jump to: navigation, search

Instructions how to enable Code10 support on SUSE Manager

Following these instructions will allow you to manage SLES10 (SP3 and SP4) clients with SUSE Manager

!! Attention - this is part of a closed beta test

!! Do NOT try this on a production system

Quick outline

The majority of steps is around adding SLES 10 repositories and channels on the server side.

Client management (registering it with the SUSE Manager Server, etc.) is supposed to be identical to SLES 11 based clients.


  • A fully updated SUSE Manager Server
 spacewalk-service stop
 zypper ref
 zypper up
  • Make sure you have plenty of disk space, the SLES10 channels are huge (~10GB)

Detailed steps (Server side)

Update to Code10-Beta1

  • Add the repo with Beta1 SUSE Manager packages
 zypper ar beta1
 zypper ref beta1
  • Allow vendor change to openSUSE Build Service
    • (The packages are not yet signed with the SUSE key, this will follow in Beta2)
 mkdir /etc/zypp/vendors.d
 cat <<EOF > /etc/zypp/vendors.d/suse-manager
 vendors = suse,openSUSE,openSUSE Build Service
  • Update Server to Code10-Beta1
 zypper up
  • Upgrade the database schema
    • this will add sles-10 and sled-10 to the list of allowed client operating systems
 /etc/init.d/oracle-xe start
  • Restart the SUSE Manager Server
 spacewalk-service start

Provide a minimal set of client packages on the server

  • During bootstrap, the client will retrieve a minimal set of packages directly from the server
    • This set is installed via a "spacewalk-client-repository-*" package on the server side
    • Run these commands on the server:
 zypper in spacewalk-client-repository-sle-10-4
 zypper in spacewalk-client-repository-sle-10-3

Re-generate (with Code10 support)

  • Navigate to Admin -> SUSE Manager Configuration -> Bootstrap Script
  • Click on 'Update'

You can either edit this file on the server or on the client (see below).

Sync the SLES 10 channels from NCC

  • ssh to the server
  • Update the channel configuration
 mgr-ncc-sync -s
  • Verify that sles10-sp{3,4}-pool-* and sles10-sp{3,4}-updates-* are listed
 mgr-ncc-sync -l
  • Add the SLES 10 channel you need
 mgr-ncc-sync -c sles10-sp4-pool-x86_64
 mgr-ncc-sync -c sles10-sp4-updates-x86_64

  • Add SLES 10 Client Tools

Pool and Update are already on NCC, the Client Tools channel not yet

  • Create activation keys
    • and assign the respective Pool, Updates, and Tools channels

Client side

Supported is SLES 10 SP3 and SP4

  • download
  • edit
    • remove the 'exit 1' line
    • fill in activation key
  • run


  • Q: bootstrap fails with 'spacewalk-check not found'
  • A: install the respective 'spacewalk-client-repository-sle-10-{3,4}' package on the server (see above)