Registering a SLES 10 SP2 server with SUSE Manager

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

Environment

SUSE Manager 2.1
SUSE Manager 1.7

Situation

Registering a SLES 10 SP2 server with SUSE Manager.

NOTE: Ongoing management of SLES 10 SP2 is not supported, this process is for the sole purpose of performing a migration to SLES 10 SP3 using SUSE Manager.  In order to accomplish that, the SLES 10 SP2 server must be registered with the SUSE Manager Server.

For a list of client versions that have support for ongoing management please see the SUSE Manager Technical Information webpage.

Resolution

The following example will illustrate the steps necessary for SLES 10 SP2 x86_64.  The specific architecture can be modified to cover your installation

I. The first step is to create the SLES 10 SP2 channels

1. In the SUSE Manager webUI go to Channels --> Manage Software Channels --> + create new channel
2. Example entries for a SLES 10 SP2 x86_64 setup:

- Channel Name: SLES 10 SP2 Pool x86_64
- Channel label: sles10-sp2-pool-x86_64
- Parent Channel: None
- Architecture: x86_64
- Channel Summary: SLES 10 SP2 Pool x86_64

3. Once the required values have been entered select Create Channel
4. We need to create the SLES 10 SP2 Updates child channel select Manage Software Channels
5. Select + create new channel
6. Example entries for a SLES 10 SP2 x86_64 setup:

- Channel Name: SLES 10 SP2 Updates x86_64
- Channel label: sles10-sp2-Updates-x86_64
- Parent Channel: SLES 10 SP2 Pool x86_64
- Architecture: x86_64
- Channel Summary: SLES 10 SP2 Updates x86_64

NOTE: the updates channel is a child of the pool channel that was created in step 2.

7. select Create Channel
8. We need to create the SLES 10 SP2 SUSE Manager Tools child channel --> select Manage Software Channels
9. Select + create new channel
10. I used the following values

- Channel Name: SLES 10 SP2 SUSE Manager Tools x86_64
- Channel label: sle10-sp2-suse-manager-tools-x86_64
- Parent Channel: SLES 10 SP2 Pool x86_64
- Architecture: x86_64
- Channel Summary: SLES 10 SP3 SUSE Manager Tools x86_64

11. Select Create Channel

II. Now that we have the channels in place we need to populate them.  This is done from the command line using the following commands (the following commands are based on the values we used in created the channels in the webUI, if you used a different channel label you will need to reflect that in the commands).  It should also be noted that SUSE Manager repositories could also be used to populate SLES 10 SP2 channels, however, this was not done in this example because the SLES 10 SP2 channels no longer receive updates (general support for SLES 10 SP2 ended April 10, 2010).

1. The following will mirror the pool repo to the SUSE Manager server

spacewalk-repo-sync -c sles10-sp2-pool-x86_64 -u https://<mirrcred user>:<mirrcred password>@nu.novell.com/repo/\$RCE/SLES10-SP2-Pool/sles-10-x86_64

mirror credentials found in your SCC account under Organization --> Organization Credentials

2. The following will mirror the updates repo

spacewalk-repo-sync -c sles10-sp2-updates-x86_64 -u https://<mirrcred user>:<mirrcred password>@nu.novell.com/repo/\$RCE/SLES10-SP2-Updates/sles-10-x86_64

3. The following will mirror the tools repositories

spacewalk-repo-sync -c sle10-sp2-suse-manager-tools-x86_64 -u https://<mirrcred user>:<mirrcred password>@nu.novell.com/repo/\$RCE/SLE10-SUSE-Manager-Tools/sles-10-x86_64

(Note: another method of creating the tools would be to simply create a clone of the SLE10-SUSE-Manager-Tools channel if you already have it mirrored, making sure that the SLES 10 SP2 Pool channel is the clone's parent)

Sync'ing will need to be done with one repo at a time and takes between 1 and 2 hours to complete both

III. While you are waiting for the sync'ing to finish we need to create a bootstrap directory for SLES 10 SP2.  You can fix that by doing the following from the terminal on the SUSE Manager server:

1. mkdir /srv/www/htdocs/pub/repositories/sle/10/2/

2. Depending on the original method used to create the repositories (ie SUSE Manager 1.7) the /srv/www/htdocs/pub/repositories/susemanager-client-setup/ directory may not exist and will need to be created.

If the /srv/www/htdocs/pub/repositories/susemanager-client-setup/ directory exists

create the following symbolic link to it in the sle/10/2/:

cd /srv/www/htdocs/pub/repositories
mkdir sle/10/2/
cd sle/10/2
ln -s ../../../susemanager-client-setup bootstrap

If the susemanager-client-setup does not exist.

In order for this to work the SLES 10 SP3 Pool and SLES 10 SP3 Updates need to be fully mirrored first:
After mirroring the SLES 10 SP3 Pool and SLES 10 SP3 Updates channels run the following:

mgr-create-bootstrap-repo
Enter product label: SLE-10-SP3-x86_64

This will create and/or update the /srv/www/htdocs/pub/repositories/sle/10/3/bootstrap/ files

cd /srv/www/htdocs/pub/repositories
mkdir sle/10/2/
cd sle/10/2
ln -s ../3/bootstrap bootstrap

If you are on SUSE Manager 2.1 that was upgraded from SUSE Manager 1.7 you are more than likely using the first method.  It is strongly suggested that you switch to the 2nd method that will keep your bootstrap repos up-to-date.  For more information on this process please see Creating Up-to-date Bootstrap Repositories in the SUSE Manager 2.1 Installation & Troubleshooting Guide.

IV.  The next step is to create an activation key for the SLES 10 SP2 systems:

In the SUSE Manager webUI go to systems --> activation keys --> create key

Continuing with our example system the following was used:

Description:    SLES 10 SP4 x86_64 Key
Key:  1-sles10sp2x64
Base Channel:  SLES 10 SP2 Pool x86_64 (NOTE SUSE Manager Default will not work here, the SLES 10 SP2 Pool we created earlier must be selected as the base channel)
Add-on Entitlements: Leave unchecked (NOTE: Only the registration, updating, and SP Migration are supported with SLES 10 SP2)
Select "Create Activation Key"

Add the child channels to the key we just created:

1. Select the key you created for SLES 10 SP2 in Manage Activation Keys
2. Select the Child Channels tab
3. Select the SLES 10 SP2 Updates x86_64 and SLES 10 SP2 SUSE Manager Tools x86_64 child channels so that they are both highlighted and select Update Keys

V.  Create a bootstrap file for the SLES 10 SP2 key just created:

1. In the SUSE Manager terminal enter the following:

mgr-bootstrap --activation-keys=1-sles10sp2x64

Replacing the 1-sles10sp2x64 with the key you used in the previous step.

NOTE: This will over write the existing /srv/www/htdocs/pub/bootstrap/bootstrap.sh file.  Before proceeding be sure to make of copy of the existing file before running the mgr-bootstrap command.

Once the bootstrap is created you can either use the default name (ie bootstrap.sh) or rename it to something more recognizable (ie bootstrap-sles10sp2x64.sh).

VI.  The next step is to run the bootstrap on the SLES 10 SP2 client

1. From a terminal on the SLES 10 SP2 client run the following:

curl -Sks http://<suse manager fqdn>/pub/bootstrap/bootstrap.sh | /bin/bash

replacing bootstrap.sh with the name of your SLES 10 SP2 bootstrap file you just created.

Once the bootstrap completes running run the following command

zypper ref --services

zypper lr should now show something similar to the following:

:~ # zypper lr
# | Alias                                         | Name                                  | Enabled | Refresh
--+-----------------------------------------------+---------------------------------------+---------+--------
1 | spacewalk:sle10-sp2-suse-manager-tools-x86_64 | SLES 10 SP2 SUSE Manager Tools x86_64 | Yes     | Yes  
2 | spacewalk:sles10-sp2-pool-x86_64              | SLES 10 SP2 Pool x86_64               | Yes     | Yes  
3 | spacewalk:sles10-sp2-updates-x86_64           | SLES 10 SP2 Updates x86_64            | Yes     | Yes  
4 | susemanager-client-setup                      | susemanager-client-setup              | Yes     | Yes 

It is recommended that you fully patch the SLES 10 SP2 system before proceeding with the SLES 10 SP3 migration.

Cause


Additional Information


Disclaimer

This Support Knowledgebase provides a valuable tool for 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:7016303
  • Creation Date: 12-Mar-2015
  • Modified Date:03-Mar-2020
    • SUSE Manager

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center