My SLED install thinks it is a different release

SUSE Linux Enterprise Desktop SLED Updates
1

I have a workstation that is running SLED12 SP3. All the update repositories were the SP3 ones but /etc/SuSE-release contains:

[CODE]SUSE Linux Enterprise Desktop 12 (x86_64)
VERSION = 12
PATCHLEVEL = 2

This file is deprecated and will be removed in a future service pack or release.

Please check /etc/os-release for details about this release.[/CODE]

and /etc/os-release contains:

NAME="SLED" VERSION="12-SP2" VERSION_ID="12.2" PRETTY_NAME="SUSE Linux Enterprise Desktop 12 SP2" ID="sled" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:suse:sled:12:sp2"

Thinking that there must be some sort of registration error I deleted the machine from the SCC subscription and re-registered it using the procedure at:https://support.microfocus.com/kb/doc.php?id=3303599

However, this replaced all the SP3 repositories with SP2 ones, so I now seem to have a SP3 install that thinks it is SP2.

uname -r gives:

4.4.162-94.72-default

I was actually trying to migrate the machine to SP4, but when I run the Yast Online Migration tool it gives the following error:

[CODE]Error
Connection to registration server failed
Details: The requested products ‘SUSE Linux Enterprise Software Development kit SP2 x86_64’ have not been activated on the system.

Error
No migration product found[/CODE]

I believe I have a fully up to date SP3 system that thinks it is SP2. Any ideas how I can resolve this?

Rob

2

Back in 2016 I upgraded some SUSE Linux Enterprise Server (SLES) 11 boxes
and had the /etc/SUSE-release files out of date, and it was because the
sles-version package had not been updated. This file in the filesystem is
owned, as I recall, by sles-release, so if that one package does not
upgrade then the file looks old, even though the system is functionally
new. In my client’s case the reason was that some packages were locked
and those could be seen in /etc/zypp/locks though you may have a different
root cause.

–
Good luck.

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

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.

3

ttrcf Wrote in message:
[color=blue]

I have a workstation that is running SLED12 SP3. All the update
repositories were the SP3 ones but /etc/SuSE-release contains:

Code:

SUSE Linux Enterprise Desktop 12 (x86_64)

VERSION = 12
PATCHLEVEL = 2

This file is deprecated and will be removed in a future service pack or release.

Please check /etc/os-release for details about this release.

and /etc/os-release contains:

Code:

NAME="SLED"

VERSION=“12-SP2”
VERSION_ID=“12.2”
PRETTY_NAME=“SUSE Linux Enterprise Desktop 12 SP2”
ID=“sled”
ANSI_COLOR=“0;32”
CPE_NAME=“cpe:/o:suse:sled:12:sp2”

Thinking that there must be some sort of registration error I deleted
the machine from the SCC subscription and re-registered it using the
procedure at:https://support.microfocus.com/kb/doc.php?id=3303599

However, this replaced all the SP3 repositories with SP2 ones, so I now
seem to have a SP3 install that thinks it is SP2.

uname -r gives:

Code:

4.4.162-94.72-default

I was actually trying to migrate the machine to SP4, but when I run the
Yast Online Migration tool it gives the following error:

Code:

Error

Connection to registration server failed
Details: The requested products ‘SUSE Linux Enterprise Software Development kit SP2 x86_64’ have not been activated on the system.

Error
No migration product found

I believe I have a fully up to date SP3 system that thinks it is SP2.
Any ideas how I can resolve this?[/color]

Presumably this workstation was originally installed as SLED12 SP2
then upgraded to SLED12 SP3? Or perhaps it was installed as an
earlier version of SLED then upgraded with subsequent releases?
Either way, how did you do the upgrade(s)?

HTH.

Simon Flood
SUSE Knowledge Partner

----Android NewsGroup Reader----
http://usenet.sinaapp.com/

4

All SP updates were applied with YaST.

I have done a clean install from the SP4 medium and all is now well. Thanks for the replies.