Upgrade SLES12 SP2 to SP3 fails

SUSE Linux Enterprise Server SLES Updates
1

Trying to update a server from SLES 12 SP2 to SP3, using “zypper migration”.

I get an error “Can’t get available migrations from server: SUSE::Connect::ApiError: The requested products ‘’ are not activated on the system” with no products listed.

Any ideas?

Thanks,

Chris.

2

On 20/12/17 15:34, cabracy wrote:
[color=blue]

Trying to update a server from SLES 12 SP2 to SP3, using “zypper
migration”.

I get an error “Can’t get available migrations from server:
SUSE::Connect::ApiError: The requested products ‘’ are not activated on
the system” with no products listed.

Any ideas?[/color]

Is your SLES12 SP2 registered? If so, with SUSE Customer Center (SCC) or
a local SUSE Manager or SMT server?

What does “zypper products” report?

HTH.

Simon
SUSE Knowledge Partner

If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

3

It is registered. It is registered to SUSE. But It is in google cloud, so it might be weird. (see below)

But I have had no other issues, installing or patching.

zypper products:

Refreshing service ‘SMT-http_smt-gce_susecloud_net’.
Refreshing service ‘cloud_update’.
Loading repository data…
Reading installed packages…
S | Repository | Internal Name | Name | Version | Arch | Is Base
—±--------------------------------------------±----------------------------------±--------------------------------------------------±--------±-------±-------
i+ | @System | sle-module-hpc | HPC Module | 12.2-0 | x86_64 | No
v | SLE-Module-Adv-Systems-Management12-Pool | sle-module-adv-systems-management | Advanced Systems Management Module | 12-0 | x86_64 | No
i+ | SLE-Module-Adv-Systems-Management12-Updates | sle-module-adv-systems-management | Advanced Systems Management Module | 12-0 | x86_64 | No
v | SLE-Module-Adv-Systems-Management12-Updates | sle-module-adv-systems-management | Advanced Systems Management Module | 12-0 | x86_64 | No
v | SLE-Module-Containers12-Pool | sle-module-containers | Containers module | 12-0 | x86_64 | No
i+ | SLE-Module-Containers12-Updates | sle-module-containers | Containers module | 12-0 | x86_64 | No
v | SLE-Module-Containers12-Updates | sle-module-containers | Containers module | 12-0 | x86_64 | No
v | SLE-Module-Containers12-Updates | sle-module-containers | Containers module | 12-0 | x86_64 | No
v | SLE-Module-Legacy12-Pool | sle-module-legacy | Legacy Module | 12-0 | x86_64 | No
i+ | SLE-Module-Legacy12-Updates | sle-module-legacy | Legacy Module | 12-0 | x86_64 | No
v | SLE-Module-Legacy12-Updates | sle-module-legacy | Legacy Module | 12-0 | x86_64 | No
v | SLE-Module-Public-Cloud12-Pool | sle-module-public-cloud | Public Cloud Module | 12-0 | x86_64 | No
i+ | SLE-Module-Public-Cloud12-Updates | sle-module-public-cloud | Public Cloud Module | 12-0 | x86_64 | No
v | SLE-Module-Public-Cloud12-Updates | sle-module-public-cloud | Public Cloud Module | 12-0 | x86_64 | No
v | SLE-Module-Toolchain12-Pool | sle-module-toolchain | Toolchain Module | 12-0 | x86_64 | No
i+ | SLE-Module-Toolchain12-Updates | sle-module-toolchain | Toolchain Module | 12-0 | x86_64 | No
v | SLE-Module-Toolchain12-Updates | sle-module-toolchain | Toolchain Module | 12-0 | x86_64 | No
v | SLE-Module-Web-Scripting12-Pool | sle-module-web-scripting | Web and Scripting Module | 12-0 | x86_64 | No
i+ | SLE-Module-Web-Scripting12-Updates | sle-module-web-scripting | Web and Scripting Module | 12-0 | x86_64 | No
v | SLE-Module-Web-Scripting12-Updates | sle-module-web-scripting | Web and Scripting Module | 12-0 | x86_64 | No
v | SLE-Module-Web-Scripting12-Updates | sle-module-web-scripting | Web and Scripting Module | 12-0 | x86_64 | No
i+ | SLE-SDK12-SP2-Pool | sle-sdk | SUSE Linux Enterprise Software Development Kit 12 | 12.2-0 | x86_64 | No
i+ | SLES12-SP2-Pool | SLES | SUSE Linux Enterprise Server 12 SP2 | 12.2-0 | x86_64 | Yes

Thanks,

Chris.

4

I am beginning the process of upgrading my 1st of 6 SLES 12 SP2 servers to SP3. The installation of all SP2 maintenance was successful and I rebooted by server (Linux on System z). The server is registered to an SMT server which is registered with SCC.

I ran ‘zypper migration’ and received the following:

Executing 'zypper  refresh'

Repository 'SLES12-SP2-12.2-0' is up to date.
Repository 'SLES12-SP2-Pool' is up to date.
Repository 'SLES12-SP2-Updates' is up to date.
All repositories have been refreshed.

Executing 'zypper  --no-refresh patch-check --updatestack-only'

Loading repository data...
Reading installed packages...

0 patches needed (0 security patches)

Can't get available migrations from server: SUSE::Connect::ApiError: Not Found[/CODE]

From a previous post it was asked for the output of 'zypper products'.

[CODE]Refreshing service 'SMT-http_wcs-mf-smt_xxx_com'.
Loading repository data...
Reading installed packages...
S  | Repository        | Internal Name | Name                                | Version | Arch  | Is Base
---+-------------------+---------------+-------------------------------------+---------+-------+--------
i+ | SLES12-SP2-12.2-0 | SLES          | SUSE Linux Enterprise Server 12 SP2 | 12.2-0  | s390x | Yes
v  | SLES12-SP2-Pool   | SLES          | SUSE Linux Enterprise Server 12 SP2 | 12.2-0  | s390x | No

Before I started the SP3 upgrade I went into YaST | Network Services | SMT Server Management and toggled on mirroring for SLES12-SP3-Pool, SLES12-SP3-Updates, and SLES12-Updates. I then selected “Mirror Now”.

What else do I need to do to continue with my upgrade?

Harley

5

Resolved!

The issue was caused by the SMT software not being patched to the most current level.

harley

6

I had similar problem which was:

Can’t get available migrations from server: SUSE::Connect::ApiError: Multiple base products found: [“SUSE Linux Enterprise Server 12 SP2 aarch64”, “SUSE Linux Enterprise Server 12 SP3 aarch64”]

This is solved by running SUSEConnect --rollback