After the server has been registered in the Customer Center, you can apply the patches. The default GNOME desktop indicates when there are updates available to the server. You can update the server from any of the following interfaces.
You could also patch an OES server using Section 8.7, Patching From Behind a Proxy Server.
After you have registered the server in the Customer Center, you can update the server by using commands at the command line. The following procedure specifies steps for updating the server with all available patches for OES.
Log in to the server as root or su to root.
At the command line, enter the following commands.
Refresh all services:
zypper ref -s
The list of repositories should include the following update repositories:
Enabled Repositories
OES2023-Pool
OES2023-SLE-Module-Basesystem15-SP4-Pool
OES2023-SLE-Module-Basesystem15-SP4-Updates
OES2023-SLE-Module-Containers15-SP4-Pool
OES2023-SLE-Module-Containers15-SP4-Updates
OES2023-SLE-Module-Desktop-Applications15-SP4-Pool
OES2023-SLE-Module-Desktop-Applications15-SP4-Updates
OES2023-SLE-Module-Server-Applications15-SP4-Pool
OES2023-SLE-Module-Server-Applications15-SP4-Updates
OES2023-SLE-Product-SLES15-SP4-Pool
OES2023-SLE-Product-SLES15-SP4-Updates
OES2023-Updates
Optional/Disabled Repositories
OES2023-SLE-Manager-Tools15-Debuginfo-Pool
OES2023-SLE-Manager-Tools15-Debuginfo-Updates
OES2023-SLE-Manager-Tools15-Pool
OES2023-SLE-Manager-Tools15-Source-Pool
OES2023-SLE-Manager-Tools15-Updates
OES2023-SLE-Module-Basesystem15-SP4-Debuginfo-Pool
OES2023-SLE-Module-Basesystem15-SP4-Debuginfo-Updates
OES2023-SLE-Module-Basesystem15-SP4-Source-Pool
OES2023-SLE-Module-Containers15-SP4-Debuginfo-Pool
OES2023-SLE-Module-Containers15-SP4-Debuginfo-Updates
OES2023-SLE-Module-Containers15-SP4-Source-Pool
OES2023-SLE-Module-Desktop-Applications15-SP4-Debuginfo-Pool
OES2023-SLE-Module-Desktop-Applications15-SP4-Debuginfo-Updates
OES2023-SLE-Module-Desktop-Applications15-SP4-Source-Pool
OES2023-SLE-Module-DevTools15-SP4-Debuginfo-Pool
OES2023-SLE-Module-DevTools15-SP4-Debuginfo-Updates
OES2023-SLE-Module-DevTools15-SP4-Pool
OES2023-SLE-Module-DevTools15-SP4-Source-Pool
OES2023-SLE-Module-DevTools15-SP4-Updates
OES2023-SLE-Module-Legacy15-SP4-Debuginfo-Pool
OES2023-SLE-Module-Legacy15-SP4-Debuginfo-Updates
OES2023-SLE-Module-Legacy15-SP4-Pool
OES2023-SLE-Module-Legacy15-SP4-Source-Pool
OES2023-SLE-Module-Legacy15-SP4-Updates
OES2023-SLE-Module-Public-Cloud15-SP4-Debuginfo-Pool
OES2023-SLE-Module-Public-Cloud15-SP4-Debuginfo-Updates
OES2023-SLE-Module-Public-Cloud15-SP4-Pool
OES2023-SLE-Module-Public-Cloud15-SP4-Source-Pool
OES2023-SLE-Module-Public-Cloud15-SP4-Updates
OES2023-SLE-Module-Python3-15-SP4-Debuginfo-Pool
OES2023-SLE-Module-Python3-15-SP4-Debuginfo-Updates
OES2023-SLE-Module-Python3-15-SP4-Pool
OES2023-SLE-Module-Python3-15-SP4-Source-Pool
OES2023-SLE-Module-Python3-15-SP4-Updates
OES2023-SLE-Module-Server-Applications15-SP4-Debuginfo-Pool
OES2023-SLE-Module-Server-Applications15-SP4-Debuginfo-Updates
OES2023-SLE-Module-Server-Applications15-SP4-Source-Pool
OES2023-SLE-Module-Web-Scripting15-SP4-Debuginfo-Pool
OES2023-SLE-Module-Web-Scripting15-SP4-Debuginfo-Updates
OES2023-SLE-Module-Web-Scripting15-SP4-Pool
OES2023-SLE-Module-Web-Scripting15-SP4-Source-Pool
OES2023-SLE-Module-Web-Scripting15-SP4-Updates
OES2023-SLE-Product-SLES15-SP4-Debuginfo-Pool
OES2023-SLE-Product-SLES15-SP4-Debuginfo-Updates
OES2023-SLE-Product-SLES15-SP4-Source-Pool
See whether updates are available for OES 2023:
zypper patch-check
This command search for the patches in all enabled repositories on the system.
To view the updates available on a specific repository, you can run the command as follows:
zypper patch-check --repo catalog1 --repo catalog2
For example,
zypper patch-check --repo OES2023-Updates
zypper patch-check --repo OES2023-SLE-Product-SLES15-SP4-Updates --repo OES2023-SLE-Module-Basesystem15-SP4-Updates
Update the server with all available OES patches:
zypper patch
Repeat Step 2.b and Step 2.c until no more updates are available.
If the patching requires a server reboot, do so when intimated by the system.
Rebooting the server activates the new kernel if it has been updated and ensures that OES services that need restarting after patching are restarted.
IMPORTANT:Always use the zypper patch command to update an OES server.
For more information on zypper, see SDB:Zypper usage 11.3.
You can also update your server with specific maintenance patches.
Log in to the server as root or su to root.
At the command line, enter the following commands:
To refresh all services, enter:
zypper ref -s
To check for available updates, enter:
zypper lu
To list the patches and their status, enter:
zypper pch
To view specific patch information, enter:
zypper patch-info patch_name
For example:
zypper patch-info SUSE-SLE-Module-Basesystem-15-SP4-2022-3307
To list all installed patches, enter:
zypper search -t patch -i
To update the server with specific patches, choose from the following:
To install all patches from one or more catalogs of a particular category:
zypper patch -g category_name
Replace category_name with security, recommended, or optional.
For example:
zypper patch -g security
To install one version of a patch without confirmation, enter:
zypper --non-interactive in -t patch patch_name-version
For example:
zypper --non-interactive in -t patch SUSE-SLE-Module-Basesystem-15-SP4-2022-3307
To install all versions of a patch, enter:
zypper in -t patch patch_name*
If the update requires a server reboot, do so when intimated by the system. This ensures that any changes to the kernel are activated, and applicable OES services are restarted.