Book-Sle-Upgrade Color en PDF

Upgrade Guide
SUSE Linux Enterprise Server 15 SP1

Upgrade Guide
SUSE Linux Enterprise Server 15 SP1
This book guides you through upgrades and updates of SUSE Linux Enterprise Serv-
er. Different approaches are described, for example upgrading from an installation
DVD, via network boot, or a running system.
Publication Date: February 28, 2020
SUSE LLC
10 Canal Park Drive
Suite 200
Cambridge MA 02141
USA
https://www.suse.com/documentation
Copyright © 2006– 2020 SUSE LLC and contributors. All rights reserved.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Docu-
mentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright
notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation
License”.
For SUSE trademarks, see http://www.suse.com/company/legal/ . All other third-party trademarks are the prop-
erty of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its affiliates.
Asterisks (*) denote third-party trademarks.
All information found in this book has been compiled with utmost attention to detail. However, this does not
guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors nor the translators shall be held liable
for possible errors or the consequences thereof.
Contents
About This Guide vi

Support Statement for SUSE Linux Enterprise Server xi • Technology
Previews xii
1 Upgrade Paths and Methods 1

1.1 Supported Upgrade Paths to SLES 15 SP1 1
1.2 Online and Offline Upgrade 3
2 Life Cycle and Support 4

2.1 Terminology 4
2.2 Product Life Cycle 6
2.3 Module Dependencies and Life Cycles 8
2.4 Generating Periodic Life Cycle Report 8
2.5 Support Levels 8
2.6 Registering and Deregistering Machines with SUSEConnect 11
2.7 Identifying the SLE Version 12
3 Preparing the Upgrade 13

3.1 Make Sure the Current System Is Up-To-Date 13
3.2 Read the Release Notes 13
3.3 Make a Backup 14
3.4 Listing Installed Packages and Repositories 14
iii Upgrade Guide

3.5 Upgrading from SUSE Linux Enterprise Server 11 SP4 15
Migrate Your MySQL Database 15 • Migrate Your PostgreSQL
Database 16 • Create Non-MD5 Server Certificates for Java
Applications 19
3.6 Shut Down Virtual Machine Guests 19
3.7 Adjusting Your SMT Client Setup 20
3.8 Disk Space 21

Checking Disk Space on Non-Btrfs File Systems 21 • Checking Disk Space on
Btrfs Root File Systems 22
3.9 Upgrading a Subscription Management Tool (SMT) Server 23
3.10 Temporarily Disabling Kernel Multiversion Support 23
3.11 Upgrading on IBM Z 23
3.12 IBM POWER: Starting an X Server 23
4 Upgrading Offline 25
4.1 Conceptual Overview 25
4.2 Starting the Upgrade from an Installation Medium 25
4.3 Starting the Upgrade from a Network Source 26

Manually Upgrading via Network Installation Source—Booting from DVD
26 • Manually Upgrading via Network Installation Source—Booting via
PXE 27
4.4 Upgrading SUSE Linux Enterprise 27

Post-upgrade Checks 29
4.5 Upgrading with AutoYaST 30
4.6 Upgrading with SUSE Manager 30
4.7 Updating Registration Status after Rollback 31
4.8 Registering Your System 31
iv Upgrade Guide
5 Upgrading Online 33
5.1 Conceptual Overview 33
5.2 Service Pack Migration Workflow 34
5.3 Canceling Service Pack Migration 35
5.4 Upgrading with the Online Migration Tool (YaST) 35
5.5 Upgrading with Zypper 37
5.6 Upgrading with Plain Zypper 39
5.7 Rolling Back a Service Pack 42
5.8 Upgrading with SUSE Manager 44
5.9 Upgrading from openSUSE Leap to SUSE Linux Enterprise Server 45
6 Backports of Source Code 47

6.1 Reasons for Backporting 47
6.2 Reasons against Backports 48
6.3 The Implications of Backports for Interpreting Version Numbers 48
6.4 Checking for Fixed Bugs and Backported Features 49
A GNU Licenses 51
A.1 GNU Free Documentation License 51
v Upgrade Guide
About This Guide
There are different ways to upgrade SUSE Linux Enterprise Server. It is impossible to cover all
combinations of boot, or installation server, automated installations or deploying images. This
manual should help with selecting the appropriate method of upgrading your installation.
Upgrade Guide
This part will give you some background information on terminology, SUSE product life-
cycles and Service Pack releases, and recommended upgrade policies.
1 Available Documentation
Note: Online Documentation and Latest Updates

Documentation for our products is available at https://documentation.suse.com/ , where
you can also nd the latest updates, and browse or download the documentation in var-
ious formats. The latest documentation updates are usually available in the English ver-
sion of the documentation.
The following documentation is available for this product:
Article “Installation Quick Start”

This Quick Start guides you step-by-step through the installation of SUSE® Linux Enter-
prise Server 15 SP1.
Book “Deployment Guide”

This guide details how to install single or multiple systems, and how to exploit the prod-
uct-inherent capabilities for a deployment infrastructure. Choose from various approach-
es: local installation from physical installation media, customizing the standard installa-
tion images, network installation server, mass deployment using a remote-controlled, high-
ly-customized, automated installation process, and initial system configuration.
Book “Administration Guide”

Covers system administration tasks like maintaining, monitoring and customizing an ini-
tially installed system.
vi Available Documentation SLES 15 SP1

Book “Virtualization Guide”
Describes virtualization technology in general, and introduces libvirt—the unified inter-
face to virtualization—and detailed information on specific hypervisors.
Book “Storage Administration Guide”

Provides information about how to manage storage devices on a SUSE Linux Enterprise
Server.
Book “AutoYaST Guide”

AutoYaST is a system for unattended mass deployment of SUSE Linux Enterprise Server
systems using an AutoYaST profile containing installation and configuration data. The
manual guides you through the basic steps of auto-installation: preparation, installation,
and configuration.
Book “Security Guide”

Introduces basic concepts of system security, covering both local and network security
aspects. Shows how to use the product inherent security software like AppArmor or the
auditing system that reliably collects information about any security-relevant events.
Book “Hardening Guide”

Deals with the particulars of installing and setting up a secure SUSE Linux Enterprise Serv-
er, and additional post-installation processes required to further secure and harden that
installation. Supports the administrator with security-related choices and decisions.
Book “System Analysis and Tuning Guide”

An administrator's guide for problem detection, resolution and optimization. Find how to
inspect and optimize your system by means of monitoring tools and how to efficiently
manage resources. Also contains an overview of common problems and solutions and of
additional help and documentation resources.
Book “Repository Mirroring Tool Guide”

An administrator's guide to Subscription Management Tool—a proxy system for SUSE Cus-
tomer Center with repository and registration targets. Learn how to install and configure a
local SMT server, mirror and manage repositories, manage client machines, and configure
clients to use SMT.
Book “GNOME User Guide”

Introduces the GNOME desktop of SUSE Linux Enterprise Server. It guides you through
using and configuring the desktop and helps you perform key tasks. It is intended mainly
for end users who want to make efficient use of GNOME as their default desktop.
vii Available Documentation SLES 15 SP1

The release notes for this product are available at https://www.suse.com/releasenotes/ .
2 Giving Feedback
Your feedback and contribution to this documentation is welcome! Several channels are avail-
able:
Service Requests and Support

For services and support options available for your product, refer to http://www.suse.com/
support/ .
To open a service request, you need a subscription at SUSE Customer Center. Go to https://
scc.suse.com/support/requests , log in, and click Create New.
Bug Reports
Report issues with the documentation at https://bugzilla.suse.com/ . To simplify this
process, you can use the Report Documentation Bug links next to headlines in the HTML ver-
sion of this document. These preselect the right product and category in Bugzilla and add
a link to the current section. You can start typing your bug report right away. A Bugzilla
account is required.
Contributions
To contribute to this documentation, use the Edit Source links next to headlines in the
HTML version of this document. They take you to the source code on GitHub, where you
can open a pull request. A GitHub account is required.
For more information about the documentation environment used for this doc-
umentation, see the repository's README (https://github.com/SUSE/doc-sle/blob/mas-
ter/README.adoc) .
Mail
Alternatively, you can report errors and send feedback concerning the documentation to
[email protected] . Make sure to include the document title, the product version and
the publication date of the documentation. Refer to the relevant section number and title
(or include the URL) and provide a concise description of the problem.
viii Giving Feedback SLES 15 SP1

3 Documentation Conventions
The following notices and typographical conventions are used in this documentation:
/etc/passwd : directory names and le names
PLACEHOLDER : replace PLACEHOLDER with the actual value
PATH : the environment variable PATH
ls , --help : commands, options, and parameters
user : users or groups
package name : name of a package
Alt , Alt – F1 : a key to press or a key combination; keys are shown in uppercase as on
a keyboard
File, File Save As: menu items, buttons
x86_64 This paragraph is only relevant for the AMD64/Intel 64 architecture. The arrows
mark the beginning and the end of the text block.
System z, POWER This paragraph is only relevant for the architectures IBM Z and POWER .
The arrows mark the beginning and the end of the text block.
Dancing Penguins (Chapter Penguins, ↑Another Manual): This is a reference to a chapter in

another manual.
Commands that must be run with root privileges. Often you can also prefix these com-
mands with the sudo command to run them as non-privileged user.
root # command
tux > sudo command
Commands that can be run by non-privileged users.
tux > command
Notices
ix Documentation Conventions SLES 15 SP1

Warning: Warning Notice
Vital information you must be aware of before proceeding. Warns you about security
issues, potential loss of data, damage to hardware, or physical hazards.
Important: Important Notice

Important information you should be aware of before proceeding.
Note: Note Notice

Additional information, for example about differences in software versions.
Tip: Tip Notice

Helpful information, like a guideline or a piece of practical advice.
4 Product Life Cycle and Support

SUSE products are supported for up to 13 years. To check the life cycle dates for your product,
see https://www.suse.com/lifecycle/ .
For SUSE Linux Enterprise, the following life cycles and release cycles apply:
SUSE Linux Enterprise Server has a 13-year life cycle: 10 years of general support and
three years of extended support.
SUSE Linux Enterprise Desktop has a 10-year life cycle: seven years of general support and
Major releases are published every four years. Service packs are published every 12-14
months.
SUSE supports previous SUSE Linux Enterprise service packs for six months after the release
of a new service pack.
x Product Life Cycle and Support SLES 15 SP1

For some products, Long Term Service Pack Support (LTSS) is available. Find information
about our support policy and options at https://www.suse.com/support/policy.html and https://
www.suse.com/support/programs/long-term-service-pack-support.html .
Modules have a different life cycle, update policy, and update timeline than their base prod-
ucts. Modules contain software packages and are fully supported parts of SUSE Linux Enterprise
Server. For more information, see the Article “Modules and Extensions Quick Start”.
4.1 Support Statement for SUSE Linux Enterprise Server

To receive support, you need an appropriate subscription with SUSE. To view the specific support
offerings available to you, go to https://www.suse.com/support/ and select your product.
The support levels are defined as follows:
L1
Problem determination, which means technical support designed to provide compatibility
information, usage support, ongoing maintenance, information gathering and basic trou-
bleshooting using available documentation.
L2
Problem isolation, which means technical support designed to analyze data, reproduce
customer problems, isolate problem area and provide a resolution for problems not re-
solved by Level 1 or prepare for Level 3.
L3
Problem resolution, which means technical support designed to resolve problems by en-
gaging engineering to resolve product defects which have been identified by Level 2 Sup-
port.
For contracted customers and partners, SUSE Linux Enterprise Server is delivered with L3 sup-
port for all packages, except for the following:
Technology Previews
Sound, graphics, fonts and artwork.
Packages that require an additional customer contract.
xi Support Statement for SUSE Linux Enterprise Server SLES 15 SP1

Some packages shipped as part of the module Workstation Extension are L2-supported only.
Packages with names ending in -devel (containing header les and similar developer
resources) will only be supported together with their main packages.
SUSE will only support the usage of original packages. That is, packages that are unchanged
and not recompiled.
4.2 Technology Previews

Technology previews are packages, stacks, or features delivered by SUSE to provide glimpses
into upcoming innovations. The previews are included for your convenience to give you the
chance to test new technologies within your environment. We would appreciate your feedback!
If you test a technology preview, please contact your SUSE representative and let them know
about your experience and use cases. Your input is helpful for future development.
However, technology previews come with the following limitations:
Technology previews are still in development. Therefore, they may be functionally incom-
plete, unstable, or in other ways not suitable for production use.
Technology previews are not supported.
Technology previews may only be available for specific hardware architectures.
Details and functionality of technology previews are subject to change. As a result, up-
grading to subsequent releases of a technology preview may be impossible and require a
fresh installation.
Technology previews can be dropped at any time. For example, if SUSE discovers that a
preview does not meet the customer or market needs, or does not prove to comply with
enterprise standards. SUSE does not commit to providing a supported version of such tech-
nologies in the future.
For an overview of technology previews shipped with your product, see the release notes at
https://www.suse.com/releasenotes/ .
xii Technology Previews SLES 15 SP1

1 Upgrade Paths and Methods
SUSE® Linux Enterprise (SLE) allows to upgrade an existing system to the new ver-
sion, for example, going from SLE 12 SP4 to the latest SLE 15 service pack. No new
installation is needed. Existing data, such as home and data directories and system
configuration, is kept intact. You can update from a local CD or DVD drive or from
a central network installation source.
This chapter explains how to manually upgrade your SUSE Linux Enterprise system,
be it by DVD, network, an automated process, or SUSE Manager.
1.1 Supported Upgrade Paths to SLES 15 SP1

Before you perform any migration, read Chapter 3, Preparing the Upgrade.
Important: Cross-architecture Upgrades Are Not Supported

Cross-architecture upgrades, such as upgrading from a 32-bit version of SUSE Linux En-
terprise Server to the 64-bit version, or upgrading from big endian to little endian are
not supported!
Specifically, SLE 11 on POWER (big endian) to SLE 15 SP1 on POWER (new: little endian!)
is not supported.
Also, since SUSE Linux Enterprise 15 SP1 is 64-bit only, upgrades from any 32-bit SUSE
Linux Enterprise 11 systems to SUSE Linux Enterprise 15 SP1 and later are not supported.
To make a cross-architecture upgrade, you need to perform a new installation.
Note: Skipping Service Packs

Consecutively installing all Service Packs is the easiest upgrade path. For the SUSE Linux
Enterprise 15 product line (GA and the following Service Packs) it is supported to skip one
service pack when upgrading. For example, it is supported to upgrade from SLE 15 GA
to 15 SP2 or from SLE 15 SP1 to 15 SP3.
1 Supported Upgrade Paths to SLES 15 SP1 SLES 15 SP1

Note: Upgrading Major Releases
We recommend to do a fresh install when upgrading to a new Major Release, for example
from SUSE Linux Enterprise 12 to SUSE Linux Enterprise 15.
Leap
Leap15
15 SLES
SLES15
15 SLES
SLES15
15SP1
SP1
SLES
SLES12
12GA
GA SLES
SLES12
12SP1
SP1 SLES
SLES12
12SP2
SP2 SLES
SLES12
12SP3
SP3 SLES
SLES12
12SP4
SP4
Only Oﬄine Upgrade

SLES
SLES11
11 SLES
SLES11
11SP4
SP4
Only Online Upgrade
FIGURE 1.1: OVERVIEW OF SUPPORTED UPGRADE PATHS
SUPPORTED UPGRADE PATHS PER VERSION
Upgrading from SUSE Linux Enterprise Server 11 GA / SP1 / SP2 / SP3

Upgrading from SLES 11 SP3 or older service packs directly is not supported. You need at
least SLES 11 SP4 before you can proceed to SLES 15 SP1.
If you cannot do a fresh installation, rst upgrade your installed SLES 11 service pack to
SLES 11 SP4. This upgrade is described in the SLES 11 Deployment Guide (https://documen-
tation.suse.com/sles-11/) .
Upgrading from SUSE Linux Enterprise Server11 SP4

Upgrading from SLES 11 SP4 is only supported via an offline upgrade. Refer to Section 1.2,
“Online and Offline Upgrade” for details.
Upgrading from SUSE Linux Enterprise Server 12 GA / SP1 / SP2

Upgrading from SLES 12 SP2 or older service packs directly is not supported. You need at
least SLES 12 SP3 before you can proceed to SLES 15 SP1.
If you cannot do a fresh installation, rst upgrade your installed SLES 12 service pack to
SLES 12 SP3. This upgrade is described in the SLES 12 Deployment Guide (https://documen-
tation.suse.com/sles-12/) .
Upgrading from SUSE Linux Enterprise Server 12 SP3 / SP4

Upgrading from SLES 12 SP3 / SP4 is only supported via an offline upgrade. Refer to
Section 1.2, “Online and Offline Upgrade” for details.
2 Supported Upgrade Paths to SLES 15 SP1 SLES 15 SP1

Upgrading SUSE Linux Enterprise Public Cloud Guests
See https://https://documentation.suse.com/suse-distribution-migration-system/1.0/sin-
gle-html/distribution-migration-system/ for instructions on upgrading SLE guests in pub-
lic clouds.
1.2 Online and Offline Upgrade

SUSE supports the following upgrade and migration methods. For more information about the
terminology, see Section 2.1, “Terminology”. The methods are:
Online
Upgrades that are executed from the running operating system itself (system up and run-
ning state). Examples: online update with Zypper or YaST, connected through SUSE Cus-
tomer Center or Repository Mirroring Tool (RMT), Salt Policy via SUSE Manager.
For details, see Chapter 5, Upgrading Online.
When migrating between Service Packs of the same major release, we suggest following
Section 5.4, “Upgrading with the Online Migration Tool (YaST)” or Section 5.5, “Upgrading with Zyp-
per”.
Offline
Upgrading offline implies that the operating system to be upgraded is not running (system
down state). Instead, the installer for the target operating system is booted (for example,
from the installation media, via network or via local boot loader), and performs the up-
grade.
For details, see Chapter 4, Upgrading Offline.
Important: SUSE Manager Clients

If your machine is managed by SUSE Manager, update it as described in the SUSE Manager
documentation. The Client Migration procedure is described in the SUSE Manager Upgrade
Guide, available at https://documentation.suse.com/suma/ .
3 Online and Offline Upgrade SLES 15 SP1

2 Life Cycle and Support
This chapter provides background information on terminology, SUSE product lifecy-

cles and Service Pack releases, and recommended upgrade policies.
2.1 Terminology
This section uses several terms. To understand the information, read the definitions below:
Backporting
Backporting is the act of adapting specific changes from a newer version of software and
applying it to an older version. The most commonly used case is fixing security holes
in older software components. Usually it is also part of a maintenance model to supply
enhancements or (less commonly) new features.
Delta RPM
A delta RPM consists only of the binary di between two defined versions of a package,
and therefore has the smallest download size. Before being installed, the full RPM package
is rebuilt on the local machine.
Downstream
A metaphor of how software is developed in the open source world (compare it with up-
stream). The term downstream refers to people or organizations like SUSE who integrate the
source code from upstream with other software to build a distribution which is then used
by end users. Thus, the software ows downstream from its developers via the integrators
to the end users.
Extensions,
Add-On Products
Extensions and third party add-on products provide additional functionality of product
value to SUSE Linux Enterprise Server. They are provided by SUSE and by SUSE partners,
and they are registered and installed on top of the base product SUSE Linux Enterprise
Server.
LTSS
LTSS is the abbreviation for Long Term Service Pack Support, which is available as an
extension for SUSE Linux Enterprise Server.
4 Terminology SLES 15 SP1

Major Release,
General Availability (GA) Version
The major release of SUSE Linux Enterprise (or any software product) is a new version
which brings new features and tools, decommissions previously deprecated components
and comes with backward-incompatible changes. Major releases for example are SUSE
Linux Enterprise 12 or 15.
Migration
Updating to a Service Pack (SP) by using the online update tools or an installation medium
to install the respective patches. It updates all packages of the installed system to the latest
state.
Migration Targets
Set of compatible products to which a system can be migrated, containing the version of
the products/extensions and the URL of the repository. Migration targets can change over
time and depend on installed extensions. Multiple migration targets can be selected, for
example SLE 15 SP1 and SES6.
Modules
Modules are fully supported parts of SUSE Linux Enterprise Server with a different life
cycle. They have a clearly defined scope and are delivered via online channel only. Regis-
tering at the SUSE Customer Center, RMT (Repository Mirroring Tool), or SUSE Manager
is a prerequisite for being able to subscribe to these channels.
Package
A package is a compressed le in rpm format that contains all les for a particular program,
including optional components like configuration, examples, and documentation.
Patch
A patch consists of one or more packages and may be applied by means of delta RPMs. It
may also introduce dependencies to packages that are not installed yet.
Service Packs (SP)

Combines several patches into a form that is easy to install or deploy. Service packs are
numbered and usually contain security fixes, updates, upgrades, or enhancements of pro-
grams.
5 Terminology SLES 15 SP1

Upstream
A metaphor of how software is developed in the open source world (compare it with down-
stream). The term upstream refers to the original project, author or maintainer of a software
that is distributed as source code. Feedback, patches, feature enhancements, or other im-
provements ow from end users or contributors to upstream developers. They decide if
the request will be integrated or rejected.
If the project members decide to integrate the request, it will show up in newer versions
of the software. An accepted request will benefit all parties involved.
If a request is not accepted, it may be for different reasons. Either it is in a state that is
not compliant with the project's guidelines, it is invalid, it is already integrated, or it is
not in the interest or roadmap of the project. An unaccepted request makes it harder for
upstream developers as they need to synchronize their patches with the upstream code.
This practice is generally avoided, but sometimes it is still needed.
Update
Installation of a newer minor version of a package, which usually contains security or bug
fixes.
Upgrade
Installation of a newer major version of a package or distribution, which brings new features.
For a distinction between the upgrade options, see Section 1.2, “Online and Offline Upgrade”.
2.2 Product Life Cycle

SUSE has the following lifecycle for products:
SUSE Linux Enterprise Server has a 13-year lifecycle: 10 years of general support and three
years of extended support.
SUSE Linux Enterprise Desktop has a 10-year lifecycle: seven years of general support and
Major releases are made every four years. Service packs are made every 12-14 months.
SUSE supports previous service packs for six months after the release of the new service pack.
Figure 2.1, “Major Releases and Service Packs” depicts some mentioned aspects.
6 Product Life Cycle SLES 15 SP1

SLES 15
SP3
SP2
SP1
GA
SLES 12 SP5
6 month overlap
SP4
SP3
SP2
SP1
GA
TIME
FIGURE 2.1: MA JOR RELEASES AND SERVICE PACKS
If you need additional time to design, validate and test your upgrade plans, Long Term Service
Pack Support can extend the support you get by an additional 12 to 36 months in 12-month
increments. This gives you a total of 2 to 5 years of support on any service pack. For details,
see Figure 2.2, “Long Term Service Pack Support”.
Update path SLES 15

Upgrade path
SP3
SP2
SP1
GA
SLES 12 SP5
SP4
SP3
SP2 Last Service Pack: General Support
up to GA + 10 years
SP1
GA
Long Term Service Pack Support (LTSS), up to 3 years
TIME
FIGURE 2.2: LONG TERM SERVICE PACK SUPPORT
For more information refer to https://www.suse.com/products/long-term-service-pack-support/ .

Refer to https://www.suse.com/lifecycle for more information about lifecycles, release frequen-
cy, and the overlay support period.
7 Product Life Cycle SLES 15 SP1

2.3 Module Dependencies and Life Cycles
For a list of modules, their dependencies and lifecycles see the Article “Modules and Extensions
Quick Start”.
2.4 Generating Periodic Life Cycle Report

SUSE Linux Enterprise Server can regularly check for changes in the support status of all installed
products and send the report via e-mail in case of changes. To generate the report, install the
zypper-lifecycle-plugin with zypper in zypper-lifecycle-plugin .
Enable the report generation on your system with systemctl :
root # systemctl enable lifecycle-report
The recipient and subject of the report e-mail, and the report generation period can be configured
in the le /etc/sysconfig/lifecycle-report with any text editor. The settings MAIL_TO
and MAIL_SUBJ define the mail recipient and subject, while DAYS sets the interval at which
the report is generated.
The report displays changes in the support status after the change occurred and not in advance.
If the change occurs right after the generation of the last report, it can take up to 14 days until
you are notified of the change. Take this into account when setting the DAYS option. Change
the following configuration entries to t your requirements:
MAIL_TO='root@localhost'
MAIL_SUBJ='Lifecycle report'
DAYS=14
The latest report is available in the le /var/lib/lifecycle/report . The le contains two
sections. The rst section informs about the end of support for used products. The second section
lists packages with their support end dates and update availability.
2.5 Support Levels

The range for extended support levels starts from year 10 and ends in year 13. These contain
continued L3 engineering level diagnosis and reactive critical bug fixes. With these support
levels, you will receive updates for trivially exploitable root exploits in the kernel and other
8 Module Dependencies and Life Cycles SLES 15 SP1

root exploits directly executable without user interaction. Furthermore, they support existing
workloads, software stacks, and hardware with limited package exclusion list. Find an overview
in Table 2.1, “Security Updates and Bug Fixes”.
TABLE 2.1: SECURITY UPDATES AND BUG FIXES
General Support for Most Recent Service General Sup- Extended

Pack (SP) port for Pre- Support
vious SP, with LTSS
with LTSS
Feature Year 1-5 Year 6-7 Year 8-10 Year 4-10 Year 10-13
Technical Yes Yes Yes Yes Yes

Services
Access to Yes Yes Yes Yes Yes

Patches and
Fixes
Access to Yes Yes Yes Yes Yes

Documen-
tation and
Knowledge
Base
Support for Yes Yes Yes Yes Yes

Existing
Stacks and
Workloads
Support for Yes Yes Limited Limited No

New Deploy- (Based on (Based on
ments partner and partner and
customer re- customer re-
quests) quests)
9 Support Levels SLES 15 SP1

vious SP, with LTSS
with LTSS
Enhancement Yes Limited Limited No No

Requests (Based on (Based on
partner and partner and
quests) quests)
Hardware En- Yes Limited Limited No No

ablement and (Based on (Based on
Optimization partner and partner and
quests) quests)
Driver up- Yes Yes Limited Limited No

dates via (Based on (Based on
SUSE Solid- partner and partner and
Driver Pro- customer re- customer re-
gram (for- quests) quests)
merly PLDP)
Backport of Yes Yes Limited N/A N/A

Fixes from (Based on
Recent SP partner and
customer re-
quests)
Critical Secu- Yes Yes Yes Yes Yes

rity Updates
10 Support Levels SLES 15 SP1

vious SP, with LTSS
with LTSS
Defect Reso- Yes Yes Limited Limited Limited

lution (Severity Lev- (Severity Lev- (Severity Lev-
el 1 and 2 de- el 1 and 2 de- el 1 and 2 de-
fects only) fects only) fects only)
2.6 Registering and Deregistering Machines with

SUSEConnect
On registration, the system receives repositories from the SUSE Customer Center (see https://
scc.suse.com/ ) or a local registration proxy like SMT. The repository names map to specific
URIs in the customer center. To list all available repositories on your system, use zypper as
follows:
root # zypper repos -u
This gives you a list of all available repositories on your system. Each repository is listed by its
alias, name and whether it is enabled and will be refreshed. The option -u gives you also the
URI from where it originated.
To register your machine, run SUSEConnect, for example:
root # SUSEConnect -r REGCODE
To deregister your machine, you can use SUSEConnect too:
root # SUSEConnect --de-register
To check your locally installed products and their status, use the following command:
root # SUSEConnect -s
11 Registering and Deregistering Machines with SUSEConnect SLES 15 SP1

2.7 Identifying the SLE Version
If you need to identify the version of an SLE installation, check the content of the le /etc/
os-release .
A machine readable XML output is available with zypper :
tux > zypper --no-remote --no-refresh --xmlout --non-interactive products -i

<?xml version='1.0'?>
<stream>
<product-list>
<product name="SLES" version="15" release="0" epoch="0" arch="x86_64"
vendor="SUSE" summary="SUSE Linux Enterprise Server 15" repo="@System"
productline="sles" registerrelease="" shortname="SLES15" flavor="" isbase="true"
installed="true"><endoflife time_t="0" text="0"/><registerflavor/><description>SUSE
Linux Enterprise offers [...]</description></product>
</product-list>
</stream>
12 Identifying the SLE Version SLES 15 SP1

3 Preparing the Upgrade
Before starting the upgrade procedure, make sure your system is properly prepared.
Among others, preparation involves backing up data and checking the release notes.
3.1 Make Sure the Current System Is Up-To-Date

Upgrading the system is only supported from the most recent patch level. Make sure the latest
system updates are installed by either running zypper patch or by starting the YaST module
Online-Update.
3.2 Read the Release Notes

In the release notes you can nd additional information on changes since the previous release
of SUSE Linux Enterprise Server. Check the release notes to see whether:
your hardware needs special considerations;
any used software packages have changed significantly;
special precautions are necessary for your installation.
The release notes also provide information that could not make it into the manual on time. They
also contain notes about known issues.
If you are skipping one or more Service Packs, check the release notes of the skipped Service
Packs as well. The release notes usually only contain the changes between two subsequent re-
leases. You can miss important changes if you are only reading the current release notes.
Find the current release notes online at https://www.suse.com/releasenotes/ .
Alternatively, nd the release notes on the installation DVD in the docu directory.
13 Make Sure the Current System Is Up-To-Date SLES 15 SP1

3.3 Make a Backup
Before updating, copy existing configuration les to a separate medium (such as tape device,
removable hard disk, etc.) to back up the data. This primarily applies to les stored in /etc
and some directories and les in /var and /opt . You may also want to write the user data
in /home (the HOME directories) to a backup medium. Back up this data as root . Only root
has read permissions for all local les.
If you have selected Update an Existing System as the installation mode in YaST, you can choose
to do a (system) backup at a later point in time. You can choose to include all modified les and
les from the /etc/sysconfig directory. However, this is not a complete backup, as all the
other important directories mentioned above are missing. Find the backup in the /var/adm/
backup directory.
3.4 Listing Installed Packages and Repositories

It is often useful to save a list of installed packages, for example when doing a fresh install of
a new major SLE release or reverting to the old version.
Be aware that not all installed packages or used repositories are available in newer releases of
SUSE Linux Enterprise. Some may have been renamed and others replaced. It is also possible
that some packages are still available for legacy purposes while another package is used by
default. Therefore some manual editing of the les might be necessary. This can be done with
any text editor.
Create a le named repositories.bak.repo containing a list of all used repositories:
root # zypper lr -e repositories.bak
Also create a le named installed-software.bak containing a list of all installed packages:
root # rpm -qa --queryformat '%{NAME}\n' > installed-software.bak
Back up both les. The repositories and installed packages can be restored with the following
commands:
root # zypper ar repositories.bak.repo

root # zypper install $(cat installed-software.bak)
14 Make a Backup SLES 15 SP1

Note: Number of Packages Increases with an Update to a New
Major Release
A system upgraded to a new major version (SLE X+1 ) may contain more packages than
the initial system (SLE X ). It will also contain more packages than a fresh installation of
SLE X+1 with the same pattern selection. Reasons for this are:
Packages were split to allow a more ne-grained package selection. For example,
37 texlive packages on SLE 11 were split into over 3000 packages on SLE 15.
When a package has been split, all new packages are installed in the upgrade case
to retain the same functionality as with the previous version. However, the new
default for a fresh installation of SLE X+1 may be to not install all packages.
Legacy packages from SLE X may be kept for compatibility reasons.
Package dependencies and the scope of patterns may have changed.
3.5 Upgrading from SUSE Linux Enterprise Server 11

SP4
If you are using MySQL, PostgreSQL or Java MD5 based certificates on SUSE Linux Enterprise
Server 11 SP4, prepare your system as described in the following sections.
3.5.1 Migrate Your MySQL Database

As of SUSE Linux Enterprise 12, SUSE switched from MySQL to MariaDB. Before you start any
upgrade, it is highly recommended to back up your database.
To perform the database migration, do the following:
1. Log in to your SUSE Linux Enterprise 11 machine.
2. Create a dump le:
root # mysqldump -u root -p --all-databases > mysql_backup.sql
15 Upgrading from SUSE Linux Enterprise Server 11 SP4 SLES 15 SP1

By default, mysqldump does not dump the INFORMATION_SCHEMA or perfor-
mance_schema database. For more details refer to https://dev.mysql.com/doc/ref-
man/5.5/en/mysqldump.html .
3. Store your dump le, the configuration le /etc/my.cnf , and the directory /etc/
mysql/ for later investigation (not installation!) in a safe place.
4. Perform your upgrade. After the upgrade, your former configuration le /etc/my.cnf is
still intact. You can nd the new configuration in the le /etc/my.cnf.rpmnew .
5. Configure your MariaDB database to your needs. Do not use the former configuration le
and directory, but use it as a reminder and adapt it.
6. Make sure you start the MariaDB server:
root # systemctl start mysql
If you want to start the MariaDB server on every boot, enable the service:
root # systemctl enable mysql
7. Verify that MariaDB is running properly by connecting to the database:
root # mysql -u root -p
3.5.2 Migrate Your PostgreSQL Database

A newer version of the PostgreSQL database is shipped with SUSE Linux Enterprise Server 15
SP1. Because of the required migration work of the database, there is no automatic upgrade
process. As such, the switch from one version to another needs to be done manually.
The migration process is conducted by the pg_upgrade command which is an alternative
method of the classic dump and reload. In comparison with the “dump & reload” method,
pg_upgrade makes the migration less time-consuming.
The program les for each PostgreSQL version are stored in different, version-dependent di-
rectories. For example, in /usr/lib/postgresql96/ for version 9.6 and in /usr/lib/post-
gresql10/ for version 10. Note that the versioning policy of PostgreSQL has changed between
the major versions 9.6 and 10. For details, see https://www.postgresql.org/support/versioning/ .
16 Migrate Your PostgreSQL Database SLES 15 SP1

Important: Upgrading from SLE 11
When upgrading from SLE 11, postgresql94 will be uninstalled and cannot be used for
the database migration to a higher PostgreSQL version. Therefore in this case make sure
to migrate the PostgreSQL database before you upgrade your system.
The procedure below describes the database migration from version 9.6 to 10. When using a
different version as start or target, replace the version numbers accordingly.
To perform the database migration, do the following:
1. Make sure the following preconditions are fulfilled:
If not already done, upgrade any package of the old PostgreSQL version to the latest
release through a maintenance update.
Create a backup of your existing database.
Install the packages of the new PostgreSQL major version. For SLE 15 SP1 this means
to install postgresql10-server and all the packages it depends on.
Install the package postgresql10-contrib which contains the command pg_up-

grade .
Make sure you have enough free space in your PostgreSQL data area, which is /var/
lib/pgsql/data by default. If space is tight, try to reduce size with the following
SQL command on each database (can take very long!):
VACUUM FULL
2. Stop the PostgreSQL server with either:
root # /usr/sbin/rcpostgresql stop
or
root # systemctl stop postgresql.service
(depending on the SLE version you use as the start version for your upgrade).
3. Rename your old data directory:
root # mv /var/lib/pgsql/data /var/lib/pgsql/data.old

4. Initialize your new database instance either manually with initdb or by starting and
stopping PostgreSQL, which will do it automatically:
root # /usr/sbin/rcpostgresql start

root # /usr/sbin/rcpostgresql stop
or
root # systemctl start postgresql.service

root # systemctl stop postgresql.service
5. If you have changed your configuration les in the old version, consider transferring these
changes to the new configuration les. This may affect the les postgresql.auto.conf ,
postgresql.conf , pg_hba.conf and pg_ident.conf . The old versions of these les are
located in /var/lib/pgsql/data.old/ , the new versions can be found in /var/lib/
pgsql/data .
Note that just copying the old configuration les is not recommended, because this may
overwrite new options, new defaults and changed comments.
6. Start the migration process as user postgres :
root # su - postgres
postgres > pg_upgrade \
--old-datadir "/var/lib/pgsql/data.old" \
--new-datadir "/var/lib/pgsql/data" \
--old-bindir "/usr/lib/postgresql96/bin/" \
--new-bindir "/usr/lib/postgresql10/bin/"
7. Start your new database instance with either:
root # /usr/sbin/rcpostgresql start
or
root # systemctl start postgresql.service
8. Check if the migration was successful. The scope of the test depends on your use case and
there is no general tool to automate this step.

9. Remove any old PostgreSQL packages and your old data directory:
root # zypper search -s postgresql96 | xargs zypper rm -u

root # rm -rf /var/lib/pgsql/data.old
3.5.3 Create Non-MD5 Server Certificates for Java Applications

During the update from SP1 to SP2, MD5-based certificates were disabled as part of a security
x. If you have certificates created as MD5, re-create your certificates with the following steps:
1. Open a terminal and log in as root .
2. Create a private key:
root # openssl genrsa -out server.key 1024
If you want a stronger key, replace 1024 with a higher number, for example, 4096 .
3. Create a certificate signing request (CSR):
root # openssl req -new -key server.key -out server.csr
4. Self-sign the certificate:
root # openssl x509 -req -days 365 -in server.csr -signkey server.key -out
server.crt
5. Create the PEM le:
root # cat server.key server.crt > server.pem
6. Place the les server.crt , server.csr , server.key , and server.pem in the respec-
tive directories where the keys can be found. For Tomcat, for example, this directory is
/etc/tomcat/ssl/ .
3.6 Shut Down Virtual Machine Guests

If your machine serves as a VM Host Server for KVM or Xen, make sure to properly shut down
all running VM Guests prior to the update. Otherwise you may not be able to access the guests
after the update.
19 Create Non-MD5 Server Certificates for Java Applications SLES 15 SP1

3.7 Adjusting Your SMT Client Setup
If the machine you want to upgrade is registered as a client against an SMT server, take care
of the following:
Check if the version of the clientSetup4SMT.sh script on your host is up to date. clientSet-
up4SMT.sh from older versions of SMT cannot manage SMT 12 clients. If you apply software
patches regularly on your SMT server, you can always nd the latest version of clientSet-
up4SMT.sh at <SMT_HOSTNAME>/repo/tools/clientSetup4SMT.sh .
In case upgrading your machine to a higher version of SUSE Linux Enterprise Server fails, de-
register the machine from the SMT server as described in Procedure 3.1. Afterward, restart the
upgrade process.
PROCEDURE 3.1: DE-REGISTERING A SUSE LINUX ENTERPRISE CLIENT FROM AN SMT SERVER
1. Log in to the client machine.
2. The following step depends on the current operating system of the client:
For SUSE Linux Enterprise 11, execute the following commands:
tux > sudo suse_register -E

tux > sudo rm -f /etc/SUSEConnect
tux > sudo rm -rf /etc/zypp/credentials.d/*
tux > sudo rm -rf /etc/zypp/repos.d/*
tux > sudo rm -f /etc/zypp/services.d/*
tux > sudo rm -f /var/cache/SuseRegister/*
tux > sudo rm -f /etc/suseRegister*
tux > sudo rm -f /var/cache/SuseRegister/lastzmdconfig.cache
tux > sudo rm -f /etc/zmd/deviceid
tux > sudo rm -f /etc/zmd/secret
For SUSE Linux Enterprise 12, execute the following commands:
tux > sudo SUSEConnect --de-register

tux > sudo SUSEConnect --cleanup
tux > sudo rm -f /etc/SUSEConnect
tux > sudo rm -rf /etc/zypp/credentials.d/*
tux > sudo rm -rf /etc/zypp/repos.d/*
tux > sudo rm -f /etc/zypp/services.d/*
3. Log in to the SMT server.
20 Adjusting Your SMT Client Setup SLES 15 SP1

4. Check if the client has successfully been de-registered by listing all client registrations:
tux > sudo smt-list-registrations
5. If the client's host name is still listed in the output of this command, get the client's Unique
ID from the rst column. (The client might be listed with multiple IDs.)
6. Delete the registration for this client:
tux > sudo smt-delete-registration -g UNIQUE_ID
7. If the client is listed with multiple IDs, repeat the step above for each of its unique IDs.
8. Check if the client has now successfully been de-registered by re-running:
tux > sudo smt-list-registrations
3.8 Disk Space

Software tends to grow from version to version. Therefore, take a look at the available partition
space before updating. If you suspect you are running short of disk space, back up your data
before increasing the available space by resizing partitions, for example. There is no general
rule regarding how much space each partition should have. Space requirements depend on your
particular partitioning profile and the software selected.
Note: Automatic Check for Enough Space in YaST

During the update procedure, YaST will check how much free disk space is available and
display a warning to the user if the installation may exceed the available amount. In that
case, performing the update may lead to an unusable system! Only if you know exactly
what you are doing (by testing beforehand), you can skip the warning and continue the
update.
3.8.1 Checking Disk Space on Non-Btrfs File Systems

Use the df command to list available disk space. For example, in Example 3.1, “List with df -h”,
the root partition is /dev/sda3 (mounted as / ).
21 Disk Space SLES 15 SP1

EXAMPLE 3.1: LIST WITH df -h
Filesystem Size Used Avail Use% Mounted on

/dev/sda3 74G 22G 53G 29% /
tmpfs 506M 0 506M 0% /dev/shm
/dev/sda5 116G 5.8G 111G 5% /home
/dev/sda1 44G 4G 40G 9% /data
3.8.2 Checking Disk Space on Btrfs Root File Systems

On a Btrfs le system, the output of df can be misleading, because in addition to the space the
raw data allocates, a Btrfs le system also allocates and uses space for metadata.
Consequently a Btrfs le system may report being out of space even though it seems that plenty
of space is still available. In that case, all space allocated for the metadata is used up. For details
on how to check for used and available space on a Btrfs le system, see Book “Storage Adminis-
tration Guide”, Chapter 1 “Overview of File Systems in Linux”, Section 1.2.2.3 “Checking for Free Space”.
For more information refer to man 8 btrfs-filesystem and https://btrfs.wiki.kernel.org/in-
dex.php/FAQ .
If you use Btrfs as root le systems on your machine, make sure there is enough free space.
Check the available space on all mounted partitions. In the worst case, an upgrade needs as
much disk space as the current root le system (without /.snapshot ) for a new snapshot.
The following recommendations have been proven:
For all le systems including Btrfs you need enough free disk space to download and install
big RPMs. The space of old RPMs are only freed after new RPMs are installed.
For Btrfs with snapshots, you need at minimum as much free space as your current instal-
lation takes. We recommend to have twice as much free space as the current installation.
If you do not have enough free space, you can try to delete old snapshots with snapper :
root # snapper list

root # snapper delete NUMBER
However, this may not help in all cases. Before migration, most snapshots occupy only
little space.
22 Checking Disk Space on Btrfs Root File Systems SLES 15 SP1

3.9 Upgrading a Subscription Management Tool
(SMT) Server
A server running SMT requires a special upgrade procedure. Please refer to Book “Repository
Mirroring Tool Guide”, Chapter 2 “Migrate from SMT to RMT” in the Repository Management Tool Guide.
3.10 Temporarily Disabling Kernel Multiversion

Support
SUSE Linux Enterprise Server allows installing multiple kernel versions by enabling the respec-
tive settings in /etc/zypp/zypp.conf . Support for this feature needs to be temporarily dis-
abled to upgrade to a service pack. When the update has successfully finished, multiversion
support can be re-enabled. To disable multiversion support, comment the respective lines in /
etc/zypp/zypp.conf . The result should look similar to:
#multiversion = provides:multiversion(kernel)
#multiversion.kernels = latest,running
To re-activate this feature after a successful update, remove the comment signs. For more in-
formation about multiversion support, refer to Book “Deployment Guide”, Chapter 21 “Installing
Multiple Kernel Versions”, Section 21.1 “Enabling and Configuring Multiversion Support”.
3.11 Upgrading on IBM Z

Upgrading a SUSE Linux Enterprise installation on IBM Z requires the Upgrade=1 kernel para-
meter, for example via the parmfile. See Book “Deployment Guide”, Chapter 5 “Installation on IBM Z”,
Section 5.4 “The Parmfile—Automating the System Configuration”.
3.12 IBM POWER: Starting an X Server

On SLES 12 for IBM POWER the display manager is configured not to start a local X Server by
default. This setting was reversed on SLES 12 SP1—the display manager now starts an X Server.
23 Upgrading a Subscription Management Tool (SMT) Server SLES 15 SP1

To avoid problems during upgrade, the SUSE Linux Enterprise Server setting is not changed
automatically. If you want the display manager to start an X Server after the upgrade, change
the setting of DISPLAYMANAGER_STARTS_XSERVER in /etc/sysconfig/displaymanager as fol-
lows:
DISPLAYMANAGER_STARTS_XSERVER="yes"
24 IBM POWER: Starting an X Server SLES 15 SP1

4 Upgrading Offline
This chapter describes how to upgrade an existing SUSE Linux Enterprise installa-
tion using YaST which is booted from an installation medium. The YaST installer
can, for example, be started from a DVD, over the network, or from the hard disk
the system resides on.
4.1 Conceptual Overview

Before upgrading your system, read Chapter 3, Preparing the Upgrade rst.
To upgrade your system, boot from an installation source, as you would do for a fresh installa-
tion. However, when the boot screen appears, you need to select Upgrade (instead of Installation).
The upgrade can be started from:
Removable Media. This includes media such as CDs, DVDs or USB mass storage devices.
For more information, see Section 4.2, “Starting the Upgrade from an Installation Medium”.
Network Resource. You can either boot from the local medium and then select the re-
spective network installation type, or boot via PXE. For more information, see Section 4.3,
“Starting the Upgrade from a Network Source”.
4.2 Starting the Upgrade from an Installation Medium

The procedure below describes booting from a DVD, but you can also use another local instal-
lation medium like an ISO image on a USB mass storage device. The medium and boot method
to select depends on the system architecture and on whether the machine has a traditional BIOS
or UEFI.
PROCEDURE 4.1: MANUALLY UPGRADING TO SUSE LINUX ENTERPRISE SERVER 15 SP1
1. Select and prepare a boot medium, see Book “Deployment Guide”.
2. Insert the Unified Installer DVD for SUSE Linux Enterprise Server 15 SP1 and boot your
machine. A Welcome screen is displayed, followed by the boot screen.
3. Optional: To force the installer to only install packages from the DVD and not from network
sources, add the boot option media_upgrade=1 .
25 Conceptual Overview SLES 15 SP1

4. Start up the system by selecting Upgrade in the boot menu.
5. Proceed with the upgrade process as described in Section 4.4, “Upgrading SUSE Linux Enter-
prise”.
4.3 Starting the Upgrade from a Network Source

To start an upgrade from a network installation source, make sure that the following require-
ments are met:
REQUIREMENTS FOR UPGRADING FROM A NETWORK INSTALLATION SOURCE
Network Installation Source

A network installation source is set up according to Book “Deployment Guide”, Chapter 16
“Setting Up a Network Installation Source”.
Network Connection and Network Services

Both the installation server and the target machine must have a functioning network con-
nection. Required network services are:
Domain Name Service
DHCP (only needed for booting via PXE, IP can be set manually during setup)
OpenSLP (optional)
Boot Medium
A bootable SUSE Linux Enterprise DVD, ISO image or functioning PXE setup. For details
about booting via PXE, see Book “Deployment Guide”, Chapter 17 “Preparing Network Boot
Environment”, Section 17.4 “Preparing the Target System for PXE Boot”. Refer to Book “Deployment
Guide”, Chapter 11 “Remote Installation” for in-depth information on starting the upgrade
from a remote server.
4.3.1 Manually Upgrading via Network Installation Source—

Booting from DVD
This procedure describes booting from a DVD as an example, but you can also use another local
installation medium like an ISO image on a USB mass storage device. The way to select the boot
method and to start up the system from the medium depends on the system architecture and on
whether the machine has a traditional BIOS or UEFI. For details, see the links below.
26 Starting the Upgrade from a Network Source SLES 15 SP1

1. Insert the Unified Installer DVD for SUSE Linux Enterprise Server 15 SP1 and boot your
machine. A Welcome screen is displayed, followed by the boot screen.
2. Select the type of network installation source you want to use (FTP, HTTP, NFS, SMB, or
SLP). Usually you get this choice by pressing F4 , but in case your machine is equipped
with UEFI instead of a traditional BIOS, you may need to manually adjust boot parameters.
For details, see Book “Deployment Guide”, Chapter 7 “Boot Parameters” and Book “Deployment
Guide”, Chapter 8 “Installation Steps”.
prise”.
4.3.2 Manually Upgrading via Network Installation Source—

Booting via PXE
To perform an upgrade from a network installation source using PXE boot, proceed as follows:
1. Adjust the setup of your DHCP server to provide the address information needed for boot-
ing via PXE. For details, see Book “Deployment Guide”, Chapter 17 “Preparing Network Boot
Environment”, Section 17.1.1 “Dynamic Address Assignment”.
2. Set up a TFTP server to hold the boot image needed for booting via PXE. Use the Installer
DVD for SUSE Linux Enterprise Server 15 SP1 for this or follow the instructions in Book
“Deployment Guide”, Chapter 17 “Preparing Network Boot Environment”, Section 17.2 “Setting Up
a TFTP Server”.
3. Prepare PXE Boot and Wake-on-LAN on the target machine.
4. Initiate the boot of the target system and use VNC to remotely connect to the installation
routine running on this machine. For more information, see Book “Deployment Guide”,
Chapter 11 “Remote Installation”, Section 11.3 “Monitoring Installation via VNC”.
prise”.
4.4 Upgrading SUSE Linux Enterprise
27 Manually Upgrading via Network Installation Source—Booting via PXE SLES 15 SP1
Before you upgrade your system, read Chapter 3, Preparing the Upgrade rst. To perform an auto-
mated migration, proceed as follows:
Note: SUSE Customer Center and Internet Connection

If the system you want to upgrade is registered against SUSE Customer Center, make
sure to have an Internet connection during the following procedure.
1. After you have booted (either from an installation medium or the network), select the
Upgrade entry on the boot screen.
Warning: Wrong Choice May Lead to Data Loss

Make sure you selected Upgrade at this point. In case you select Installation by mis-
take, your data partition will be overwritten with a fresh installation.
YaST starts the installation system.
2. On the Welcome screen, choose Language and Keyboard. Proceed with Next.
YaST checks your partitions for already installed SUSE Linux Enterprise systems.
3. On the Select for Upgrade screen, select the partition to upgrade and click Next.
4. YaST mounts the selected partition and displays the license agreement for the upgraded
product. To continue, accept the license.
5. On the Previously Used Repositories screen, adjust the status of the repositories. By default
all repositories are removed. If you have not added any custom repositories, do not change
the settings. The packages for the upgrade will be installed from DVD, and you can op-
tionally enable the default online repositories in the next step.
If you have custom repositories, you have two choices:
Leave the repository in state Removed. Software that was installed from this reposi-
tory will be removed during the upgrade. Use this method if no version of the repos-
itory that matches the new release is available.
Update and enable the repository if it matches the new release. Change its URL by
clicking the repository in the list, and then click Change. Enable the repository by
checking Toggle Status until it is set to Enable.
28 Upgrading SUSE Linux Enterprise SLES 15 SP1

Do not keep repositories from the previous release, as the system may be unstable or not
work at all. Then proceed by clicking Next.
6. The next step depends on whether the upgraded system is registered against SUSE Cus-
tomer Center or not.
a. If the system is not registered against SUSE Customer Center, YaST displays a pop-up
message suggesting using a second installation medium, the SLE-15-SP1-Packages
image.
If you do not have that medium the system cannot be upgraded without registration.
b. If the system is registered against SUSE Customer Center, YaST will show possible
migration targets and a summary.
Select one migration target from the list and proceed with Next.
7. In the next dialog you can optionally add an additional installation medium. If you have
additional installation media, activate the I would like to install an additional Add On Product
option and specify the media type.
8. Review the Installation Settings for the upgrade.
9. If all settings are according to your wishes, start the installation and removal procedure
by clicking Update.
Tip: Upgrade Failure on SMT Clients

If the machine to upgrade is an SMT client, and the upgrade fails, see Procedure 3.1,
“De-registering a SUSE Linux Enterprise Client from an SMT Server” and restart the upgrade
procedure afterward.
10. After the upgrade process has finished successfully, perform post-upgrade checks as de-
scribed in Section 4.4.1, “Post-upgrade Checks”.
4.4.1 Post-upgrade Checks

Check for any “orphaned packages”. Orphaned packages are packages which belong to no
active repository anymore. The following command gives you a list of these:
tux > zypper packages --orphaned
29 Post-upgrade Checks SLES 15 SP1

With this list, you can decide if a package is still needed or can be uninstalled safely.
Check for any *.rpmnew and *.rpmsave les, examine their content, and possibly merge
desirable changes. When an upgrade includes changes to a default configuration le, in-
stead of overwriting the configuration le, the package will write one of these le types.
While *.rpmnew contains the new default configuration and leaves your original le un-
touched, *.rpmsave is a copy of your original configuration that has been replaced by
the new default le.
You do not need to search the whole le system for *.rpmnew and *.rpmsave les, the
most important are stored in the /etc directory. Use the following command to list them:
tux > find /etc -print | egrep "rpmnew$|rpmsave$"
4.5 Upgrading with AutoYaST

The upgrade process can be executed automatically. For details, see Book “AutoYaST Guide”, Chap-
ter 4 “Configuration and Installation Options”, Section 4.10 “Upgrade”.
4.6 Upgrading with SUSE Manager

SUSE Manager is a server solution for providing updates, patches, and security fixes for SUSE
Linux Enterprise clients. It comes with a set of tools and a Web-based user interface for man-
agement tasks. See https://www.suse.com/products/suse-manager/ for more information about
SUSE Manager.
With SUSE Manager you can perform a system upgrade. With the integrated AutoYaST technol-
ogy, upgrades from one major version to the next are possible.
documentation. The Client Migration procedure is described in the SUSE Manager Upgrade Guide,
available at https://documentation.suse.com/suma/ .
30 Upgrading with AutoYaST SLES 15 SP1

4.7 Updating Registration Status after Rollback
When performing a service pack upgrade, it is necessary to change the configuration on the
registration server to provide access to the new repositories. If the upgrade process is interrupted
or reverted (via restoring from a backup or snapshot), the information on the registration server
is inconsistent with the status of the system. This may lead to you being prevented from accessing
update repositories or to wrong repositories being used on the client.
When a rollback is done via Snapper, the system will notify the registration server to ensure
access to the correct repositories is set up during the boot process. If the system was restored with
another method, or the communication with the registration server failed, trigger the rollback
on the client manually. An example for manually triggering a rollback can be that the server
was not accessible because of network issues. To do a rollback, execute:
tux > sudo snapper rollback
We suggest always checking that the correct repositories are set up on the system, especially
after refreshing the service using:
tux > sudo zypper ref -s
This functionality is available in the rollback-helper package.
4.8 Registering Your System

If the system was not registered before running the upgrade you can register your system at any
time using the Product Registration module in YaST.
Registering your systems has these advantages:
Eligibility for support
Availability of security updates and bug fixes
Access to SUSE Customer Center
1. Start YaST and select Software Product Registration to open the Registration dialog.
2. Provide the E-mail address associated with the SUSE account you or your organization
uses to manage subscriptions. In case you do not have a SUSE account yet, go to the SUSE
Customer Center home page (https://scc.suse.com/ ) to create one.
31 Updating Registration Status after Rollback SLES 15 SP1

3. Enter the Registration Code you received with your copy of SUSE Linux Enterprise Server.
4. If one or more local registration servers are available on your network, you can choose
one of them from a list.
5. To start the registration, proceed with Next.

After successful registration, YaST lists extensions, add-ons, and modules that are available
for your system. To select and install them, proceed with Book “Deployment Guide”, Chap-
ter 20 “Installing Modules, Extensions, and Third Party Add-On Products”, Section 20.1 “Installing
Modules and Extensions from Online Channels”.
32 Registering Your System SLES 15 SP1

5 Upgrading Online
SUSE offers an intuitive graphical and a simple command line tool to upgrade a
running system to a new service pack. They provide support for “rollback” of ser-
vice packs and more. This chapter explains how to do a service pack upgrade step
by step with these tools.
5.1 Conceptual Overview

SUSE releases new service packs for the SUSE Linux Enterprise family at regular intervals. To
make it easy for customers to migrate to a new service pack and minimize downtime, SUSE
supports migrating online while the system is running.
Starting with SLE 12, YaST Wagon has been replaced by YaST migration (GUI) and Zypper
migration (command line). This has the following advantages:
The system is always in a defined state until the rst RPM is updated.
Canceling is possible until the rst RPM is updated.
Simple recovery, if there is an error.
It is possible to do a “rollback” via system tools—no backup or restore needed.
Use of all active repositories.
The ability to skip a service pack
Warning: Online Migration Not Supported for Major Releases

The online migration is only supported for migrating between service packs. Online mi-
gration is not supported for upgrading to new major releases. For details, see Chapter 1,
Upgrade Paths and Methods.
Use the offline migration to upgrade to a new major release. For details, see Chapter 4,
Upgrading Offline.
33 Conceptual Overview SLES 15 SP1

Important: Upgrading SUSE Manager Clients
If the system to upgrade is a SUSE Manager client, it cannot be upgraded by YaST
online migration nor zypper migration . Use the Client Migration procedure instead.
It is described in the SUSE Manager Upgrade Guide, available at https://documenta-
tion.suse.com/suma/ .
5.2 Service Pack Migration Workflow

A service pack migration can be executed by either YaST, zypper , or AutoYaST.
Before you can start a service pack migration, your system must be registered at the SUSE
Customer Center or a local RMT server. SUSE Manager can also be used.
Regardless of the method, a service pack migration consists of the following steps:
1. Find possible migration targets on your registered systems.
2. Select one migration target.
3. Request and enable new repositories.
4. Run the migration.
The list of migration targets depends on the products you have installed and registered. If you
have an extension installed for which the new SP is not yet available, it could be that no migra-
tion target is offered to you.
The list of migration targets available for your host will always be retrieved from the SUSE
Customer Center and depend on products or extensions installed.
34 Service Pack Migration Workflow SLES 15 SP1

5.3 Canceling Service Pack Migration
A service pack migration can only be canceled at specific stages during the migration process:
1. Until the package upgrade starts, there are only minimal changes on the system, like for
services and repositories. Restore /etc/zypp/repos.d/* to revert to the former state.
2. After the package upgrade starts, you can revert to the former state by using a Snapper
snapshot (see Book “Administration Guide”, Chapter 7 “System Recovery and Snapshot Manage-
ment with Snapper”).
3. After the migration target was selected, SUSE Customer Center changes the repository
data. To revert this state manually, use SUSEConnect --rollback .
5.4 Upgrading with the Online Migration Tool (YaST)

To perform a service pack migration with YaST, use the Online Migration tool. By default, YaST
does not install any packages from a third-party repository. If a package was installed from
a third-party repository, YaST prevents packages from being replaced with the same package
coming from SUSE.
Note: Reduce Installation Size

When performing the Service Pack migration, YaST will install all recommended pack-
ages. Especially in the case of custom minimal installations, this may increase the instal-
lation size of the system significantly.
To change this default behavior and allow only required packages, adjust the solver.on-
lyRequires option in /etc/zypp/zypp.conf .
solver.onlyRequires = true
Additionally, edit the le /etc/zypp/zypper.conf and change the installRecom-

mends option.
installRecommends=false
This changes the behavior of all package operations, such as the installation of patches
or new packages. To change the behavior of Zypper for a single invocation, add the pa-
rameter --no-recommends to your command line.
35 Canceling Service Pack Migration SLES 15 SP1

To start the service pack migration, do the following:
1. Deactivate all unused extensions on your registration server to avoid future dependency
conflicts. In case you forget an extension, YaST will later detect unused extension repos-
itories and deactivate them.
2. If you are logged in to a GNOME session running on the machine you are going to up-
date, switch to a text console. Running the update from within a GNOME session is not
recommended. Note that this does not apply when being logged in from a remote machine
(unless you are running a VNC session with GNOME).
3. If you are an LTSS subscriber, make sure that the LTSS extension repository is active.
4. Run YaST online update to get the latest package updates for your system.
5. Install the package yast2-migration and its dependencies (in YaST under Software Soft-
ware Management).
6. Restart YaST, otherwise the newly installed module will not be shown in the control center.
7. In YaST, choose Online Migration (depending on the version of SUSE Linux Enterprise
Server that you are upgrading from, this module is categorized under either System or
Software). YaST will show possible migration targets and a summary. If more than one
migration target is available for your system, select one from the list.
8. Select one migration target from the list and proceed with Next.
9. In case the migration tool offers update repositories, it is recommended to proceed with
Yes.
10. If the Online Migration tool nds obsolete repositories coming from DVD or a local server,
it is highly recommended to disable them. Obsolete repositories are from a previous SP.
Any old repositories from SUSE Customer Center or RMT are removed automatically.
11. Check the summary and proceed with the migration by clicking Next. Confirm with Start
Update.
12. After the successful migration restart your system.
36 Upgrading with the Online Migration Tool (YaST) SLES 15 SP1

5.5 Upgrading with Zypper
To perform a service pack migration with Zypper, use the command line tool zypper migra-
tion from the package zypper-migration-plugin .
Note: Reduce Installation Size

When performing the Service Pack migration, YaST will install all recommended pack-
ages. Especially in the case of custom minimal installations, this may increase the instal-
lation size of the system significantly.
To change this default behavior and allow only required packages, adjust the solver.on-
lyRequires option in /etc/zypp/zypp.conf .
solver.onlyRequires = true
Additionally, edit the le /etc/zypp/zypper.conf and change the installRecom-

mends option.
installRecommends=false
This changes the behavior of all package operations, such as the installation of patches
or new packages. To change the behavior of Zypper for a single invocation, add the pa-
rameter --no-recommends to your command line.
To start the service pack migration, do the following:
1. If you are logged in to a GNOME session running on the machine you are going to up-
date, switch to a text console. Running the update from within a GNOME session is not
recommended. Note that this does not apply when being logged in from a remote machine
(unless you are running a VNC session with GNOME).
2. Register your SUSE Linux Enterprise machine if you have not done so:
tux > sudo SUSEConnect --regcode YOUR_REGISTRATION_CODE
3. If you are an LTSS subscriber, make sure that the LTSS extension repository is active.
4. Run zypper migration :
tux > sudo zypper migration
37 Upgrading with Zypper SLES 15 SP1

Executing 'zypper patch-check --updatestack-only'
Refreshing service 'Basesystem_Module_15_x86_64'.

Refreshing service 'Desktop_Applications_Module_15_x86_64'.
Refreshing service 'SUSE_Linux_Enterprise_Server_15_x86_64'.
Refreshing service 'Server_Applications_Module_15_x86_64'.
Loading repository data...
Reading installed packages...
0 patches needed (0 security patches)
Executing 'zypper refresh'
Repository 'SLE-Module-Basesystem15-Pool' is up to date.

Repository 'SLE-Module-Basesystem15-Updates' is up to date.
Repository 'SLE-Module-Desktop-Applications15-Pool' is up to date.
Repository 'SLE-Module-Desktop-Applications15-Updates' is up to date.
Repository 'SLE-Product-SLES15-Pool' is up to date.
Repository 'SLE-Product-SLES15-Updates' is up to date.
Repository 'SLE-Module-Server-Applications15-Pool' is up to date.
Repository 'SLE-Module-Server-Applications15-Updates' is up to date.
All repositories have been refreshed.
Available migrations:
1 | SUSE Linux Enterprise Server 15 SP2 x86_64

Basesystem Module 15 SP2 x86_64
Desktop Applications Module 15 SP2 x86_64
Python 2 Module 15 SP2 x86_64
Server Applications Module 15 SP2 x86_64
2 | SUSE Linux Enterprise Server 15 SP1 x86_64

Basesystem Module 15 SP1 x86_64
Desktop Applications Module 15 SP1 x86_64
Python 2 Module 15 SP1 x86_64
Server Applications Module 15 SP1 x86_64
[num/q]:
38 Upgrading with Zypper SLES 15 SP1

Some notes about the migration process:
If more than one migration target is available for your system, Zypper allows you
to select one SP from the list. This is the same as skipping one or more SPs. Keep
in mind, online migration for base products (SLES, SLED) remains available only
between the SPs of a major version.
By default, Zypper uses the option --no-allow-vendor-change which is passed to

zypper dup . If a package was installed from a third-party repository, this option
prevents packages from being replaced with the same package coming from SUSE.
If Zypper nds obsolete repositories coming from DVD or a local server, it is highly
recommended to disable them. Old SUSE Customer Center or RMT repositories are
removed automatically.
5. Review all the changes, especially the packages that are going to be removed. Proceed by
typing y (the exact number of packages to upgrade can vary on your system):
266 packages to upgrade, 54 to downgrade, 17 new, 8 to reinstall, 5 to remove, 1 to

change arch.
Overall download size: 285.1 MiB. Already cached: 0 B After the operation,
additional 139.8 MiB will be used.
Continue? [y/n/? shows all options] (y):
Use the Shift – Page ↑ or Shift – Page ↓ keys to scroll in your shell.
6. After successful migration restart your system.
5.6 Upgrading with Plain Zypper

If your system is not registered because you do not have access to the Internet or a registration
server, migrating to a new service pack is not possible with YaST Migration or zypper mi-
gration . In this case you can still migrate to a new service pack with plain Zypper and some
manual interactions.
39 Upgrading with Plain Zypper SLES 15 SP1

Important: For Unregistered Systems Only
This migration path to a new service pack is only supported for unregistered systems that
do not have access to the Internet or a registration server. This may, for example, be the
case for machines in a specially protected network. In case you have a registered system,
use YaST or Zypper migration.
Important: Installation Sources

This migration path requires you to provide the installation sources for the new service
pack in a place that can be accessed by the machine you are going to migrate. This can
for example be achieved by setting up an RMT server or an SLP server.
It is also required that the system has access to an up-to-date update repository for the
installed product version.
1. If you are logged in to a graphical session running on the machine you are going to migrate,
log out of that session and switch to a text console. Running the update from within a
graphical session is not recommended. Note that this does not apply when being logged
in from a remote machine (unless you are running a VNC session with X).
2. Update the package management tools with the old SUSE Linux Enterprise repositories:
tux > sudo zypper patch --updatestack-only
3. Get a list of packages that currently do not have a repository assigned to them (orphaned
packages). These packages will not be migrated and there is no guarantee that they will
work after the migration (because other packages they rely on may have changed in a way
they are no longer compatible). To get the list, run
tux > sudo zypper packages --orphaned
Carefully review the list and remove all orphaned packages that are no longer needed.
Make a note of all remaining orphaned packages, you will need it later for comparison.
4. Get a list of all repositories that the system is currently subscribed to by running:
tux > sudo zypper repos -u

In the following you need to rewrite the repository URLs so they point to the respective
repositories for the new service pack ( SLE-15 needs to be replaced with SLE-15-SP1 . If
the URL for a repository looks like this:
http://rmt.example.com/repo/SUSE/Products/SLE-15-Product-SLES/x86_64/product/
it needs to be changed to
http://rmt.example.com/repo/SUSE/Products/SLE-15-SP1-Product-SLES/x86_64/product/
This needs to be done with all repositories that are enabled. You may want to consider also
doing this for repositories that are currently disabled, to avoid having wrong installation
sources in the system when activating them at a later point in time.
To change the repository URLs you have the following options:
a. Using YaST Software Software Repositories. Select a repository and click Edit to
make the required change. Repeat this for all repositories.
b. Using Zypper. Add a new repository and remove the corresponding old one after-
wards:
tux > sudo zypper addrepo -f URL NAME-15-SP1

tux > sudo zypper removerepo NAME
c. By editing repository configuration les in /etc/zypp/repos.d . Each repository is

represented by one configuration le. Changing the value for the baseurl parameter
is required in each le.
5. Review your changes by running zypper repos -u and update the repositories by run-
ning:
tux > sudo zypper refresh -f -s
In case updating a repository fails, double-check whether you entered the wrong URL. If
the problem cannot be xed, it is recommended to disable the failing repository.
If all repositories are correctly configured, run
tux > sudo zypper refresh -f -s
again, to make sure all repositories are up-to-date.

6. Before starting the migration it is recommended do a test run rst:
tux > sudo zypper dup -D --no-allow-vendor-change --no-recommends
The parameter -D will perform a dry-run, that simulates the migration without actually
changing the system. In case problems occur, x them before proceeding. In case the test
run succeeds, perform the real migration by running
tux > sudo zypper dup --no-allow-vendor-change --no-recommends
-no-allow-vendor-change ensures that third-party RPMs will not overwrite RPMs from
the base system. The option --no-recommends ensures that packages deselected during
initial installation will not be added again.
7. When the migration has finished and the system has booted into the new service pack
version, run the check for orphaned packages again:
tux > sudo zypper packages --orphaned
Compare the new list with the one you generated before starting the migration. In case
new packages appear in the list, it may be because they were moved to a different module
in the new service pack. In case you did not have that module in the previous installation,
the package did not get updated.
You can check to which module a package belongs at https://scc.suse.com/packages . Add
the missing modules using zypper addrepo or the YaST Software Repositories module,
and update the orphaned packages afterwards by running:
tux > sudo zypper install --no-recommends LIST OF PACKAGES
8. You have successfully migrated to a new service pack!
5.7 Rolling Back a Service Pack

If a service pack does not work for you, SUSE Linux Enterprise supports reverting the system to
the state before the service pack migration was started. Prerequisite is a Btrfs root partition with
snapshots enabled (this has been the default since SLES 12). See Book “Administration Guide”,
Chapter 7 “System Recovery and Snapshot Management with Snapper” for details.
42 Rolling Back a Service Pack SLES 15 SP1

1. Get a list of all Snapper snapshots:
tux > sudo snapper list
Review the output to locate the snapshot that was created immediately before the service
pack migration was started. The column Description contains a corresponding statement
and the snapshot is marked as important in the column Userdata. Memorize the snapshot
number from the column # and its date from the column Date.
2. Reboot the system. From the boot menu, select Start boot loader from a read-only snapshot
and then choose the snapshot with the date and number you memorized in the previous
step. A second boot menu (the one from the snapshot) is loaded. Select the entry starting
with SLES 15 SP1 and boot it.
3. The system boots into the previous state with the system partition mounted read-only.
Log in as root and check whether you have chosen the correct snapshot. Also make sure
everything works as expected. Note that since the root le system is mounted read-only,
restrictions in functionality may apply.
In case of problems or if you have booted the wrong snapshot, reboot and choose a different
snapshot to boot from—up to this point no permanent changes have been made. If the
snapshot is correct and works as expected, make the change permanent by running the
following command:
tux > sudo snapper rollback
Reboot afterward. On the boot screen, choose the default boot entry to reboot into the
reinstated system.
4. Check if the repository configuration has been properly reset. Furthermore, check if all
products are properly registered. If either one is not the case, updating the system at a
later point in time may no longer work, or the system may be updated using the wrong
package repositories.
Make sure the system can access the Internet before starting this procedure.
a. Refresh services and repositories by running
tux > sudo zypper ref -fs
b. Get a list of active repositories by running
43 Rolling Back a Service Pack SLES 15 SP1

tux > sudo zypper lr
Carefully check the output of this command. No services and repositories that were
added for the update should be listed. For example, if you are rolling back from
SLES15 SP1 to SLES15, the list must contain the SLES15 repositories, and not the
SLES15-SP1 repositories.
If wrong repositories are listed, delete them and, if necessary, replace them with the
versions matching your product or service pack version. For a list of repositories
for the supported migration paths refer to Section 2.3, “Module Dependencies and Life
Cycles”. (Note that manual intervention should not be necessary, as the repositories
should be updated automatically, but it is a best practice to verify and make any
necessary corrections.)
c. Last, check the registration status for all products installed by running
tux > sudo SUSEConnect --status
All products should be reported as being Registered . If this is not the case, repair
the registration by running
tux > sudo SUSEConnect --rollback
Now you have successfully reverted the system to the state that was captured immediately before
the service pack migration was started.
5.8 Upgrading with SUSE Manager

SUSE Manager is a server solution for providing updates, patches, and security fixes for SUSE
Linux Enterprise clients. It comes with a set of tools and a Web-based user interface for man-
agement tasks. See https://www.suse.com/products/suse-manager/ for more information about
SUSE Manager.
SP Migration allows migrating from one Service Pack (SP) to another within one major version
(for example, from SLES 15 GA to SLES 15 SP1).
documentation. The Client Migration procedure is described in the SUSE Manager Upgrade Guide,
available at https://documentation.suse.com/suma/ .
44 Upgrading with SUSE Manager SLES 15 SP1

5.9 Upgrading from openSUSE Leap to SUSE Linux
Enterprise Server
You can upgrade an openSUSE installation online to SUSE Linux Enterprise Server. The proce-
dure is analogous to Section 5.5, “Upgrading with Zypper”, but some additional steps are required.
Before executing this procedure on a production system, we recommend to rst run it on a test
system that replicates your production setup.
To see for which openSUSE Leap versions a migration is supported, read Section 1.1, “Supported
Upgrade Paths to SLES 15 SP1”.
Warning: Not All openSUSE Packages Can Be Migrated

The openSUSE repositories provide more packages than are available in the SUSE Linux
Enterprise Server repositories. If you have any of these packages installed, they will no
longer receive updates after the migration. These packages will be removed when follow-
ing the procedure below.
Make sure that all packages you need for operating your system are available in the SUSE
Linux Enterprise Server repository. You can also check if the packages are available in
the SUSE Package Hub repository. For details, see Book “Deployment Guide”, Chapter 20
“Installing Modules, Extensions, and Third Party Add-On Products”, Section 20.3 “SUSE Package
Hub”.
To migrate from openSUSE Leap, execute the following procedure:
1. Switch to a TTY, for example by pressing Ctrl – Alt – F1 . Then log in as root .
2. Install SUSEConnect .
root # zypper in SUSEConnect
3. Register at SCC to get the SUSE Linux Enterprise Server repositories.
root # SUSEConnect -r REGISTRATION_CODE -p SLES/15.1/x86_64
4. List and disable all openSUSE repositories on your system.
root # zypper lr
root # zypper mr -d REPO_IDS
45 Upgrading from openSUSE Leap to SUSE Linux Enterprise Server SLES 15 SP1
Replace REPO_IDS with a space character separated list of all enabled openSUSE repos-
itories.
5. Now add the modules you need for your installation.
root # SUSEConnect --list-extensions

[...]
root # SUSEConnect -p sle-module-basesystem/15.1/x86_64
To have replacements for most Leap packages, we recommend to enable the Basesystem,
Desktop Applications, Server Applications and Legacy modules. Additionally, we recom-
mend to enable the SUSE Package Hub.
6. Migrate installed packages to the SUSE Linux Enterprise Server repositories.
root # zypper dup --force-resolution
7. Remove orphaned packages.
root # zypper rm $(zypper --no-refresh packages --orphaned | gawk '{print $5}' |

tail -n +5)
8. Finally, reboot the system.
46 Upgrading from openSUSE Leap to SUSE Linux Enterprise Server SLES 15 SP1
6 Backports of Source Code
SUSE extensively uses backports, for example for the migration of current software
fixes and features into released SUSE Linux Enterprise packages. The information in
this chapter explains why it can be misleading to compare version numbers to judge
the capabilities and the security of SUSE Linux Enterprise software packages. This
chapter also explains how SUSE keeps the system software secure and current while
maintaining compatibility for your application software on top of SUSE Linux Enter-
prise products. You will also learn how to check which public security issues actu-
ally are addressed in your SUSE Linux Enterprise system software, and the current
status of your software.
6.1 Reasons for Backporting

Upstream developers are primarily concerned with advancing the software they develop. Often
they combine fixing bugs with introducing new features which have not yet received extensive
testing and which may introduce new bugs.
For distribution developers, it is important to distinguish between:
bugfixes with a limited potential for disrupting functionality; and
changes that may disrupt existing functionality.
Usually, distribution developers do not follow all upstream changes when a package has become
part of a released distribution. Usually they stick instead with the upstream version that they
initially released and create patches based on upstream changes to x bugs. This practice is
known as backporting.
Distribution developers generally will only introduce a newer version of software in two cases:
when the changes between their packages and the upstream versions have become so large
that backporting is no longer feasible, or
for software that inherently ages badly, like anti-malware software.
47 Reasons for Backporting SLES 15 SP1

SUSE uses backports extensively as we strike a good balance between several concerns for en-
terprise software. The most important of them are:
Having stable interfaces (APIs) that software vendors can rely on when building products
for use on SUSE's enterprise products.
Ensuring that packages used in the release of SUSE's enterprise products are of the highest
quality and have been thoroughly tested, both in themselves and as part of the whole
enterprise product.
Maintaining the various certifications of SUSE's enterprise products by other vendors, like
certifications for Oracle or SAP products.
Allowing SUSE's developers to focus on making the next product version, rather than
spreading their focus thinly across a wide range of releases.
Keeping a clear view of what is in a particular enterprise release, so that our support can
provide accurate and timely information about it.
6.2 Reasons against Backports

It is a general policy rule that no new upstream versions of a package are introduced into our
enterprise products. This rule is not an absolute rule however. For certain types of packages, in
particular anti-virus software, security concerns weigh heavier than the conservative approach
that is preferable from the perspective of quality assurance. For packages in that class, occasion-
ally newer versions are introduced into a released version of an enterprise product line.
Sometimes also for other types of packages the choice is made to introduce a new version rather
than a backport. This is done when producing a backport is not economically feasible or when
there is a very relevant technical reason to introduce the newer version.
6.3 The Implications of Backports for Interpreting

Version Numbers
Because of the practice of backporting, one cannot simply compare version numbers to deter-
mine whether a SUSE package contains a x for a particular issue or has had a particular feature
added to it. With backporting, the upstream part of a SUSE package's version number merely
48 Reasons against Backports SLES 15 SP1

indicates what upstream version the SUSE package is based on. It may contain bug fixes and
features that are not in the corresponding upstream release, but that have been backported into
the SUSE package.
One particular area where this limited value of version numbers when backporting is involved
can cause problems is with security scanning tools. Some security vulnerability scanning tools
(or particular tests in such tools) operate solely on version information. These tools and tests are
therefore prone to generating “false positives” (when a piece of software is incorrectly identified
as vulnerable) when backports are involved. When evaluating reports from security scanning
tools, always check whether an entry is based on a version number or on an actual vulnerability
test.
6.4 Checking for Fixed Bugs and Backported Features

There are several locations where information regarding backported bug fixes and features are
stored:
The package's changelog:
tux > rpm -q --changelog name-of-installed-package

tux > rpm -qp --changelog packagefile.rpm
The output briey documents the change history of the package.
The package changelog may contain entries like bsc#1234 (“Bugzilla Suse.Com”) that
refer to bugs in SUSE's Bugzilla tracking system or links to other bugtracking systems.
Because of confidentiality policies, not all such information may be accessible to you.
A package may contain a /usr/share/doc/PACKAGENAME/README.SUSE le which con-

tains general, high-level information specific to the SUSE package.
The RPM source package contains the patches that were applied during the building of the
regular binary RPMs as separate les that can be interpreted if you are familiar with read-
ing source code. See Book “Administration Guide”, Chapter 6 “Managing Software with Command
Line Tools”, Section 6.1.3.5 “Installing or Downloading Source Packages” for installing sources of
SUSE Linux Enterprise software. See Book “Administration Guide”, Chapter 6 “Managing Soft-
49 Checking for Fixed Bugs and Backported Features SLES 15 SP1

ware with Command Line Tools”, Section 6.2.5 “Installing and Compiling Source Packages” for build-
ing packages on SUSE Linux Enterprise. See the Maximum RPM (http://www.rpm.org/max-
rpm/) book for details about software package builds for SUSE Linux Enterprise.
For security bug fixes, consult the SUSE security announcements (http://www.suse.com/
support/security/#1) . These often refer to bugs through standardized names like
CAN-2005-2495 which are maintained by the Common Vulnerabilities and Exposures (CVE)
(http://cve.mitre.org) project.
50 Checking for Fixed Bugs and Backported Features SLES 15 SP1

A GNU Licenses
formats that can be read and edited only by proprietary word processors, SGML or XML for
This appendix contains the GNU Free Docu- which the DTD and/or processing tools are not generally available, and the machine-generat-
ed HTML, PostScript or PDF produced by some word processors for output purposes only.
mentation License version 1.2. The "Title Page" means, for a printed book, the title page itself, plus such following pages as
are needed to hold, legibly, the material this License requires to appear in the title page. For
works in formats which do not have any title page as such, "Title Page" means the text near the
GNU Free Documentation License most prominent appearance of the work's title, preceding the beginning of the body of the text.
A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely
Copyright (C) 2000, 2001, 2002 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, XYZ or contains XYZ in parentheses following text that translates XYZ in another language.
Boston, MA 02110-1301 USA. Everyone is permitted to copy and distribute verbatim copies (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements",
of this license document, but changing it is not allowed. "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when
you modify the Document means that it remains a section "Entitled XYZ" according to this
definition.
0. PREAMBLE
The Document may include Warranty Disclaimers next to the notice which states that this
The purpose of this License is to make a manual, textbook, or other functional and useful License applies to the Document. These Warranty Disclaimers are considered to be included
document "free" in the sense of freedom: to assure everyone the effective freedom to copy by reference in this License, but only as regards disclaiming warranties: any other implication
and redistribute it, with or without modifying it, either commercially or non-commercially. that these Warranty Disclaimers may have is void and has no effect on the meaning of this
Secondarily, this License preserves for the author and publisher a way to get credit for their License.
work, while not being considered responsible for modifications made by others.
This License is a kind of "copyleft", which means that derivative works of the document must 2. VERBATIM COPYING
themselves be free in the same sense. It complements the GNU General Public License, which
is a copyleft license designed for free software. You may copy and distribute the Document in any medium, either commercially or non-
We have designed this License to use it for manuals for free software, because free software commercially, provided that this License, the copyright notices, and the license notice saying
needs free documentation: a free program should come with manuals providing the same this License applies to the Document are reproduced in all copies, and that you add no other
freedoms that the software does. But this License is not limited to software manuals; it can conditions whatsoever to those of this License. You may not use technical measures to obstruct
be used for any textual work, regardless of subject matter or whether it is published as a or control the reading or further copying of the copies you make or distribute. However, you
printed book. We recommend this License principally for works whose purpose is instruction may accept compensation in exchange for copies. If you distribute a large enough number of
or reference. copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly
display copies.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium, that contains a notice placed 3. COPYING IN QUANTITY
by the copyright holder saying it can be distributed under the terms of this License. Such a
notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under If you publish printed copies (or copies in media that commonly have printed covers) of the
the conditions stated herein. The "Document", below, refers to any such manual or work. Any Document, numbering more than 100, and the Document's license notice requires Cover Texts,
member of the public is a licensee, and is addressed as "you". You accept the license if you you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts:
copy, modify or distribute the work in a way requiring permission under copyright law. Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers
A "Modified Version" of the Document means any work containing the Document or a portion must also clearly and legibly identify you as the publisher of these copies. The front cover
of it, either copied verbatim, or with modifications and/or translated into another language. must present the full title with all words of the title equally prominent and visible. You may
add other material on the covers in addition. Copying with changes limited to the covers, as
A "Secondary Section" is a named appendix or a front-matter section of the Document that
long as they preserve the title of the Document and satisfy these conditions, can be treated
deals exclusively with the relationship of the publishers or authors of the Document to the
as verbatim copying in other respects.
Document's overall subject (or to related matters) and contains nothing that could fall directly
within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a If the required texts for either cover are too voluminous to t legibly, you should put the
Secondary Section may not explain any mathematics.) The relationship could be a matter rst ones listed (as many as t reasonably) on the actual cover, and continue the rest onto
of historical connection with the subject or with related matters, or of legal, commercial, adjacent pages.
philosophical, ethical or political position regarding them. If you publish or distribute Opaque copies of the Document numbering more than 100, you
The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being must either include a machine-readable Transparent copy along with each Opaque copy, or
those of Invariant Sections, in the notice that says that the Document is released under this state in or with each Opaque copy a computer-network location from which the general net-
License. If a section does not t the above definition of Secondary then it is not allowed to be work-using public has access to download using public-standard network protocols a complete
designated as Invariant. The Document may contain zero Invariant Sections. If the Document Transparent copy of the Document, free of added material. If you use the latter option, you
does not identify any Invariant Sections then there are none. must take reasonably prudent steps, when you begin distribution of Opaque copies in quanti-
ty, to ensure that this Transparent copy will remain thus accessible at the stated location until
The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or
at least one year after the last time you distribute an Opaque copy (directly or through your
Back-Cover Texts, in the notice that says that the Document is released under this License. A
agents or retailers) of that edition to the public.
Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.
It is requested, but not required, that you contact the authors of the Document well before
A "Transparent" copy of the Document means a machine-readable copy, represented in a for-
redistributing any large number of copies, to give them a chance to provide you with an
mat whose specification is available to the general public, that is suitable for revising the doc-
updated version of the Document.
ument straightforwardly with generic text editors or (for images composed of pixels) generic
paint programs or (for drawings) some widely available drawing editor, and that is suitable
for input to text formatters or for automatic translation to a variety of formats suitable for
input to text formatters. A copy made in an otherwise Transparent le format whose markup,
or absence of markup, has been arranged to thwart or discourage subsequent modification
by readers is not Transparent. An image format is not Transparent if used for any substantial
amount of text. A copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain ASCII without markup, Tex-
info input format, LaTeX input format, SGML or XML using a publicly available DTD, and stan-
dard-conforming simple HTML, PostScript or PDF designed for human modification. Examples
of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary
51 SLES 15 SP1
The author(s) and publisher(s) of the Document do not by this License give permission to use
4. MODIFICATIONS
their names for publicity for or to assert or imply endorsement of any Modified Version.
You may copy and distribute a Modified Version of the Document under the conditions of
sections 2 and 3 above, provided that you release the Modified Version under precisely this 5. COMBINING DOCUMENTS
License, with the Modified Version filling the role of the Document, thus licensing distribution
and modification of the Modified Version to whoever possesses a copy of it. In addition, you You may combine the Document with other documents released under this License, under
must do these things in the Modified Version: the terms defined in section 4 above for modified versions, provided that you include in the
combination all of the Invariant Sections of all of the original documents, unmodified, and
A. Use in the Title Page (and on the covers, if any) a title distinct from that of the
list them all as Invariant Sections of your combined work in its license notice, and that you
Document, and from those of previous versions (which should, if there were any,
preserve all their Warranty Disclaimers.
be listed in the History section of the Document). You may use the same title as a
previous version if the original publisher of that version gives permission. The combined work need only contain one copy of this License, and multiple identical Invari-
ant Sections may be replaced with a single copy. If there are multiple Invariant Sections with
B. List on the Title Page, as authors, one or more persons or entities responsible for the same name but different contents, make the title of each such section unique by adding
authorship of the modifications in the Modified Version, together with at least ve at the end of it, in parentheses, the name of the original author or publisher of that section if
of the principal authors of the Document (all of its principal authors, if it has fewer known, or else a unique number. Make the same adjustment to the section titles in the list of
than ve), unless they release you from this requirement. Invariant Sections in the license notice of the combined work.
C. State on the Title page the name of the publisher of the Modified Version, as the In the combination, you must combine any sections Entitled "History" in the various original
publisher. documents, forming one section Entitled "History"; likewise combine any sections Entitled
"Acknowledgements", and any sections Entitled "Dedications". You must delete all sections
D. Preserve all the copyright notices of the Document.
Entitled "Endorsements".
E. Add an appropriate copyright notice for your modifications adjacent to the other
copyright notices.
6. COLLECTIONS OF DOCUMENTS
F. Include, immediately after the copyright notices, a license notice giving the public
permission to use the Modified Version under the terms of this License, in the form You may make a collection consisting of the Document and other documents released under
shown in the Addendum below. this License, and replace the individual copies of this License in the various documents with a
single copy that is included in the collection, provided that you follow the rules of this License
G. Preserve in that license notice the full lists of Invariant Sections and required Cover
for verbatim copying of each of the documents in all other respects.
Texts given in the Document's license notice.
You may extract a single document from such a collection, and distribute it individually under
H. Include an unaltered copy of this License. this License, provided you insert a copy of this License into the extracted document, and follow
this License in all other respects regarding verbatim copying of that document.
I. Preserve the section Entitled "History", Preserve its Title, and add to it an item
stating at least the title, year, new authors, and publisher of the Modified Version
as given on the Title Page. If there is no section Entitled "History" in the Document, 7. AGGREGATION WITH INDEPENDENT WORKS
create one stating the title, year, authors, and publisher of the Document as given
on its Title Page, then add an item describing the Modified Version as stated in A compilation of the Document or its derivatives with other separate and independent docu-
the previous sentence. ments or works, in or on a volume of a storage or distribution medium, is called an "aggregate"
if the copyright resulting from the compilation is not used to limit the legal rights of the com-
J. Preserve the network location, if any, given in the Document for public access to
pilation's users beyond what the individual works permit. When the Document is included in
a Transparent copy of the Document, and likewise the network locations given in
an aggregate, this License does not apply to the other works in the aggregate which are not
the Document for previous versions it was based on. These may be placed in the
themselves derivative works of the Document.
"History" section. You may omit a network location for a work that was published
at least four years before the Document itself, or if the original publisher of the If the Cover Text requirement of section 3 is applicable to these copies of the Document, then
version it refers to gives permission. if the Document is less than one half of the entire aggregate, the Document's Cover Texts
may be placed on covers that bracket the Document within the aggregate, or the electronic
K. For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title equivalent of covers if the Document is in electronic form. Otherwise they must appear on
of the section, and preserve in the section all the substance and tone of each of the printed covers that bracket the whole aggregate.
contributor acknowledgements and/or dedications given therein.
L. Preserve all the Invariant Sections of the Document, unaltered in their text and 8. TRANSLATION
in their titles. Section numbers or the equivalent are not considered part of the
section titles. Translation is considered a kind of modification, so you may distribute translations of the
M. Delete any section Entitled "Endorsements". Such a section may not be included Document under the terms of section 4. Replacing Invariant Sections with translations requires
in the Modified Version. special permission from their copyright holders, but you may include translations of some
or all Invariant Sections in addition to the original versions of these Invariant Sections. You
N. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in may include a translation of this License, and all the license notices in the Document, and
title with any Invariant Section. any Warranty Disclaimers, provided that you also include the original English version of this
O. Preserve any Warranty Disclaimers. License and the original versions of those notices and disclaimers. In case of a disagreement
between the translation and the original version of this License or a notice or disclaimer, the
If the Modified Version includes new front-matter sections or appendices that qualify as Se- original version will prevail.
condary Sections and contain no material copied from the Document, you may at your option
If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the
designate some or all of these sections as invariant. To do this, add their titles to the list of
requirement (section 4) to Preserve its Title (section 1) will typically require changing the
Invariant Sections in the Modified Version's license notice. These titles must be distinct from
actual title.
any other section titles.
You may add a section Entitled "Endorsements", provided it contains nothing but endorse-
ments of your Modified Version by various parties--for example, statements of peer review
9. TERMINATION
or that the text has been approved by an organization as the authoritative definition of a
You may not copy, modify, sublicense, or distribute the Document except as expressly pro-
standard.
vided for under this License. Any other attempt to copy, modify, sublicense or distribute the
You may add a passage of up to ve words as a Front-Cover Text, and a passage of up to 25
Document is void, and will automatically terminate your rights under this License. However,
words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only
parties who have received copies, or rights, from you under this License will not have their
one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through
licenses terminated so long as such parties remain in full compliance.
arrangements made by) any one entity. If the Document already includes a cover text for the
same cover, previously added by you or by arrangement made by the same entity you are
acting on behalf of, you may not add another; but you may replace the old one, on explicit
permission from the previous publisher that added the old one.
52 SLES 15 SP1
10. FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions of the GNU Free Documen-
tation License from time to time. Such new versions will be similar in spirit to the present
version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/
copyleft/ .
Each version of the License is given a distinguishing version number. If the Document specifies
that a particular numbered version of this License "or any later version" applies to it, you have
the option of following the terms and conditions either of that specified version or of any
later version that has been published (not as a draft) by the Free Software Foundation. If the
Document does not specify a version number of this License, you may choose any version ever
published (not as a draft) by the Free Software Foundation.
ADDENDUM: How to use this License for your documents
Copyright (c) YEAR YOUR NAME.

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2
or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
A copy of the license is included in the section entitled “GNU
Free Documentation License”.
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the
“with...Texts.” line with this:
with the Invariant Sections being LIST THEIR TITLES, with the
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
If you have Invariant Sections without Cover Texts, or some other combination of the three,
merge those two alternatives to suit the situation.
If your document contains nontrivial examples of program code, we recommend releasing
these examples in parallel under your choice of free software license, such as the GNU General
Public License, to permit their use in free software.
53 SLES 15 SP1

Book-Sle-Upgrade Color en PDF

Uploaded by

Copyright:

Available Formats

Book-Sle-Upgrade Color en PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Book-Sle-Upgrade Color en PDF

Uploaded by

Copyright:

Available Formats

Upgrade Guide

SUSE Linux Enterprise Server 15 SP1

Publication Date: February 28, 2020

About This Guide vi

1 Upgrade Paths and Methods 1

1.2 Online and Offline Upgrade 3

2 Life Cycle and Support 4

2.2 Product Life Cycle 6

2.3 Module Dependencies and Life Cycles 8

2.4 Generating Periodic Life Cycle Report 8

2.5 Support Levels 8

2.6 Registering and Deregistering Machines with SUSEConnect 11

2.7 Identifying the SLE Version 12

3 Preparing the Upgrade 13

3.2 Read the Release Notes 13

3.3 Make a Backup 14

3.4 Listing Installed Packages and Repositories 14

iii Upgrade Guide

3.6 Shut Down Virtual Machine Guests 19

3.7 Adjusting Your SMT Client Setup 20

3.8 Disk Space 21

3.9 Upgrading a Subscription Management Tool (SMT) Server 23

3.10 Temporarily Disabling Kernel Multiversion Support 23

3.11 Upgrading on IBM Z 23

3.12 IBM POWER: Starting an X Server 23

4.2 Starting the Upgrade from an Installation Medium 25

4.3 Starting the Upgrade from a Network Source 26

4.4 Upgrading SUSE Linux Enterprise 27

4.5 Upgrading with AutoYaST 30

4.6 Upgrading with SUSE Manager 30

4.7 Updating Registration Status after Rollback 31

4.8 Registering Your System 31

5.2 Service Pack Migration Workflow 34

5.3 Canceling Service Pack Migration 35

5.4 Upgrading with the Online Migration Tool (YaST) 35

5.5 Upgrading with Zypper 37

5.6 Upgrading with Plain Zypper 39

5.7 Rolling Back a Service Pack 42

5.8 Upgrading with SUSE Manager 44

5.9 Upgrading from openSUSE Leap to SUSE Linux Enterprise Server 45

6 Backports of Source Code 47

6.2 Reasons against Backports 48

6.3 The Implications of Backports for Interpreting Version Numbers 48

6.4 Checking for Fixed Bugs and Backported Features 49

Note: Online Documentation and Latest Updates

The following documentation is available for this product:

Article “Installation Quick Start”

Book “Deployment Guide”

Book “Administration Guide”

vi Available Documentation SLES 15 SP1

Book “Storage Administration Guide”

Book “AutoYaST Guide”

Book “Security Guide”

Book “Hardening Guide”

Book “System Analysis and Tuning Guide”

Book “Repository Mirroring Tool Guide”

Book “GNOME User Guide”

vii Available Documentation SLES 15 SP1

Service Requests and Support