SLES11 SP2 update to SLES11 SP3 Patch level unchanged

SUSE Linux Enterprise Server SLES Updates
1

Hello - Upgraded SLES11 SP2 to SLES11 SP3 and /etc/SuSE-release PATCHLEVEL = 2 did not change to PATCHLEVEL = 3!
Initially had a problem with meta data on the SP3 repositories. Fix that.

Downloaded files:
libgpg-error0-1.10-0.7.29.s390x.rpm
libgpg-error0-32bit-1.10-0.7.29.s390x.rpm
suse-build-key-1.0-907.42.35.noarch.rpm

Executed:
libgpg-error0-1.10-0.7.29.s390x.rpm
libgpg-error0-32bit-1.10-0.7.29.s390x.rpm
suse-build-key-1.0-907.42.35.noarch.rpm

ran Yast Update - This ran well without errors.
Unsure where to start looking for how to verify PATCHLEVEL and why /etc/SuSE-release did not get updated!

uname -a
Linux linux212 3.0.101-0.47.55-default #1 SMP Thu May 28 08:25:11 UTC 2015 (dc083ee) s390x s390x s390x GNU/Linux

SUSE Linux Enterprise Server 11 (s390x)
VERSION = 11
PATCHLEVEL = 2

rpm -qa| grep release
lsb-release-2.0-1.2.18
sles-release-11.2-1.538
release-notes-sles-11.3.34-0.7.1
sles-release-DVD-11.1-1.152

2

On 08/07/2015 20:04, mikenash wrote:
[color=blue]

Hello - Upgraded SLES11 SP2 to SLES11 SP3 and /etc/SuSE-release
PATCHLEVEL = 2 did not change to PATCHLEVEL = 3![/color]

How did you upgrade from SLES11 SP2 to SP3?

Was this server originally installed as SLES11 SP2 or upgraded from an
earlier version of SLES?
[color=blue]

Initially had a problem with meta data on the SP3 repositories. Fix
that.[/color]

Please explain more about the problem and how you fixed it.
[color=blue]

Downloaded files:
libgpg-error0-1.10-0.7.29.s390x.rpm
libgpg-error0-32bit-1.10-0.7.29.s390x.rpm
suse-build-key-1.0-907.42.35.noarch.rpm

Executed:
libgpg-error0-1.10-0.7.29.s390x.rpm
libgpg-error0-32bit-1.10-0.7.29.s390x.rpm
suse-build-key-1.0-907.42.35.noarch.rpm[/color]

Why these three files?
[color=blue]

ran Yast Update - This ran well without errors.
Unsure where to start looking for how to verify PATCHLEVEL and why
/etc/SuSE-release did not get updated!

uname -a
Linux linux212 3.0.101-0.47.55-default #1 SMP Thu May 28 08:25:11 UTC
2015 (dc083ee) s390x s390x s390x GNU/Linux

SUSE Linux Enterprise Server 11 (s390x)
VERSION = 11
PATCHLEVEL = 2

rpm -qa| grep release
lsb-release-2.0-1.2.18
sles-release-11.2-1.538
release-notes-sles-11.3.34-0.7.1
sles-release-DVD-11.1-1.152[/color]

Well unsurprising your /etc/SuSE-release is incorrect as that
corresponds with the incorrect sles-release package. Also your
sles-release-DVD package is incorrect though matches SP1 not SP2!

Based on this last bit I’m therefore guessing that your server was at
least originally installed as SLES11 SP1 then upgraded to SP2? If so,
which process did you follow to do that?

What do “zypper lr -u” and “zypper se -st product” 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

Originally had a SLES11 SP1 system and updated Yast with SP2 updates. However, some packages were missing so I add more repositories.

1 | s11dvd1 | s11dvd1 | Yes | Yes | 99 | yast2 | ftp://mikenash2@ftp3install.linux.ibm.com/%2fsuse/temp_mounts/SLES-11-DVD-s390x-GM-DVD1.iso.OButmW/ | 2 | s11sp1pool | s11sp1pool | Yes | Yes | 99 | rpm-md | ftp://mikenash2@ftp3install.linux.ibm.com/%2fsuse/catalogs/SLES11-SP1-Pool/sle-11-s390x/ | 3 | s11sp1updates | s11sp1updates | Yes | Yes | 99 | rpm-md | ftp://mikenash2@ftp3install.linux.ibm.com/%2fsuse/catalogs/SLES11-SP1-Updates/sle-11-s390x/ | 4 | s11sp2core | s11sp2core | Yes | Yes | 99 | rpm-md | ftp://mikenash2@ftp3install.linux.ibm.com/%2fsuse/catalogs/SLES11-SP2-Core/sle-11-s390x/ | 5 | s11sp2updates_1 | s11sp2updates | Yes | Yes | 99 | rpm-md | ftp://mikenash2@ftp3install.linux.ibm.com/%2fsuse/catalogs/SLES11-SP2-Updates/sle-11-s390x/ |
This appeared to work. Showed the PATCHLEVEL = 2.
Added the SLES11 SP3 UPDATES and POOL repositories but yast complained about metadata.
I found a forum item that had a simular problem and adapted the information to my problem.
This appear to work except that the PATCHLEVEL did not change.
Tried to update the system with these three file:
sles-release-11.3-1.138.s390x.rpm,
sles-release-DVD-11.3-1.138.s390x.rpm,
and release-notes-sles-11.3.22-0.7.2.s390x.rpm
Tried with rpm -Uvh and zypper update but they were not found even though I found them in the POOL repository. Refresh did not help.
I was going to ftp the packages today to install but the website is down.
I had a similar problem on another system where the release packages did not install. A known problem with updates.

4

On 09/07/2015 16:34, mikenash wrote:
[color=blue]

Originally had a SLES11 SP1 system and updated Yast with SP2 updates.
However, some packages were missing so I add more repositories.

Code:

 1 | s11dvd1         | s11dvd1       | Yes     | Yes     |   99     | yast2  |

ftp://mikenash2@ftp3install.linux.ibm.com/%2Fsuse/temp_mounts/SLES-11-DVD-s390x-GM-DVD1.iso.OButmW/ |
2 | s11sp1pool | s11sp1pool | Yes | Yes | 99 | rpm-md |
ftp://mikenash2@ftp3install.linux.ibm.com/%2Fsuse/catalogs/SLES11-SP1-Pool/sle-11-s390x/ |
3 | s11sp1updates | s11sp1updates | Yes | Yes | 99 | rpm-md |
ftp://mikenash2@ftp3install.linux.ibm.com/%2Fsuse/catalogs/SLES11-SP1-Updates/sle-11-s390x/ |
4 | s11sp2core | s11sp2core | Yes | Yes | 99 | rpm-md |
ftp://mikenash2@ftp3install.linux.ibm.com/%2Fsuse/catalogs/SLES11-SP2-Core/sle-11-s390x/ |
5 | s11sp2updates_1 | s11sp2updates | Yes | Yes | 99 | rpm-md |

ftp://mikenash2@ftp3install.linux.ibm.com/%2Fsuse/catalogs/SLES11-SP2-Updates/sle-11-s390x/

This appeared to work. Showed the PATCHLEVEL = 2.
Added the SLES11 SP3 UPDATES and POOL repositories but yast complained
about metadata.
I found a forum item that had a simular problem and adapted the
information to my problem.
This appear to work except that the PATCHLEVEL did not change.
Tried to update the system with these three file:
sles-release-11.3-1.138.s390x.rpm,
sles-release-DVD-11.3-1.138.s390x.rpm,
and release-notes-sles-11.3.22-0.7.2.s390x.rpm
Tried with rpm -Uvh and zypper update but they were not found even
though I found them in the POOL repository. Refresh did not help.
I was going to ftp the packages today to install but the website is
down.
I had a similar problem on another system where the release packages did
not install.[/color]

From the above it sounds like to upgrade you simply added the repos for
the next version and then updated all the packages or have I
misunderstood? If that is the case then it explains your problems as
that’s not the correct (or supported) method to upgrade.

Perhaps you could confirm whether you followed
https://www.suse.com/documentation/sles11/book_sle_deployment/data/sec_update_sle11sp1.html
when upgrading from SLES11 SP1 to SP2 and
https://www.suse.com/documentation/sles11/book_sle_deployment/data/sec_update_sle11sp2.html
to then go from SP2 to SP3.
[color=blue]

A known problem with updates.[/color]

Not in my experience.

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.

5

On the IBM repository site there are instructions for Suse updates. I updated the repository using YAST and then went to YAST UPDATE. This is from SLES11 SP1 to SLES11 SP2. Yast complained about missing packages. To get the update to work I had to include additional repositories. Going from SLES11 SP2 to SLES11 SP3 I had the metadata problem. After resolving that problem I had the SLES release problem. I resolve that by ftp the packages and installing them.

[CODE]How to Configure YaST Online Update for SLES/SLED 10 and 11
Here is the current recipe for updating your SLES/SLED 10 and 11 boxes. Please provide feedback using the feedback link if you experience issues using the update server

  1. Run ‘yast2 inst_source’ from the command line, or start up the yast gui and click ‘installation source’
  2. Add a new FTP source
  3. Use ‘ftp3install.linux.ibm.com’ for the server
  4. For the directory, you have to choose between the following options:
    For SLES 10 and SLED 10 system, find the directory:
    ‘suse/catalogs/SLE-Updates/sle-/’
    Replace:
    for ‘S10’ or ‘D10’.
    for ‘s-10’ or ‘d-10’.
    for ‘i586’, ‘ia64’, ‘ppc’, ‘s390x’ or ‘x86_64’ when available.
    For SLES 10 and SLED 10 SP system , find the directory:
    ‘suse/catalogs/SLE-SP-Updates/sle-/’
    Replace:
    for ‘S10’ or ‘D10’.
    for ‘s-10’ or ‘d-10’.
    for ‘1’, ‘2’ or ‘3’
    for ‘i586’, ‘ia64’, ‘ppc’, ‘s390x’ or ‘x86_64’ when available.
    Additionally for SP2 or SP3 you need to add another installation source with the path ‘suse/catalogs/SLE-SP-Pool/-/’.
    For SLES 11 and SLED 11 system, find the directory:
    ‘suse/catalogs/SLE-Updates/sle-11-/’
    Replace:
    for ‘S11’ or ‘D11’.
    for ‘i586’, ‘ia64’, ‘ppc64’, ‘s390x’ or ‘x86_64’ when available.
    For SLES 11 and SLED 11 SP system , find the directory:
    ‘suse/catalogs/SLE-SP1-Updates/sle-11-/’
    Replace:
    for ‘S11’ or ‘D11’.
    for ‘i586’, ‘ia64’, ‘ppc64’, ‘s390x’ or ‘x86_64’ when available.
    Additionally for SP1 you need to add another installation source with the path ‘suse/catalogs/SLE-SP1-Pool/sle-11-/’.
    For development catalogs SLES or SLED, 10 and 11 systems, use the same syntax above, adding the -SDK after the version.
    Example:
    ‘suse/catalogs/SLE-SDK-Updates/sle-/’
  5. Use your ftp3 alternate id and password for authentication
  6. Run ‘yast2 online_update’ from the command line, or select ‘online update’ from the yast GUI.
    Note: If you want to update your SLES or SLED 10 or 11 to a SP (e.g. SP1), you must use the SP iso.[/CODE]
    The instructions that you provided reference YAST wagon. Is this different from the YAST menuwhere I select Online Update?
    Would this differ from zypper update?
6

I decided to restore the system back to SLES11 SP1 and restart the update process. I notices a SLSE11 update repository so I started here. I added the SLES11 DVD1 and SLES11 UPDATES to the repository list and I executed Online Update. It took a couple of updates. I did a reboot on the system. Then I added SLES11 SP1 updates and SLES11 SP1 Pool the repository list. Then I execute Online Update. It took a lot of updates. I did a reboot of the system. Then I added SLES11SP@ updates and SLES11 SP2 Core to the repository list. I kept the SP1 repository enabled because SP2 complained of missing packages. Then I execute Online Update. It took a lot of updates. I rebooted the system. Then I added SLES11 SP3 Updates and SLES11 SP3 Pool to the repository list. This complained about the metadata. I searched again and found this information: Document ID:7013434 Attempting to register or run a zypper ref returns Valid metadata not found at specified URL(s). The corrective actions worked last time but then I had the problem with the sles-release packages not being installed. I would like verification that I should perform the corrective actions listed in Document ID:7013434. Also, should SLES11 SP2 expect to acquire packages from SP1? Still new to this but I might expect the SP2 repositories to have all that the needed.

7

On 13/07/2015 19:04, mikenash wrote:
[color=blue]

I decided to restore the system back to SLES11 SP1 and restart the
update process. I notices a SLSE11 update repository so I started here.
I added the SLES11 DVD1 and SLES11 UPDATES to the repository list and I
executed Online Update. It took a couple of updates. I did a reboot on
the system. Then I added SLES11 SP1 updates and SLES11 SP1 Pool the
repository list. Then I execute Online Update. It took a lot of
updates. I did a reboot of the system. Then I added SLES11SP@ updates
and SLES11 SP2 Core to the repository list. I kept the SP1 repository
enabled because SP2 complained of missing packages. Then I execute
Online Update. It took a lot of updates. I rebooted the system. Then
I added SLES11 SP3 Updates and SLES11 SP3 Pool to the repository list.
This complained about the metadata. I searched again and found this
information: Document ID:7013434 Attempting to register or run a zypper
ref returns Valid metadata not found at specified URL(s). The
corrective actions worked last time but then I had the problem with the
sles-release packages not being installed. I would like verification
that I should perform the corrective actions listed in Document
ID:7013434. Also, should SLES11 SP2 expect to acquire packages from
SP1? Still new to this but I might expect the SP2 repositories to have
all that the needed.[/color]

The above all sounds like you followed your earlier steps to upgrade the
server which is not SUSE’s supported procedures which I earlier posted
the links to[1][2].

As for confusion with SLES11 SP2 requiring access to SLES11 SP1 repos,
yes that is the case - see TID 7010225[3]. Fortunately SUSE fixed that
with SLES11 SP3.

HTH.

[1]
https://www.suse.com/documentation/sles11/book_sle_deployment/data/sec_update_sle11sp1.html
[2]
https://www.suse.com/documentation/sles11/book_sle_deployment/data/sec_update_sle11sp2.html
[3] https://www.suse.com/support/kb/doc.php?id=7010225

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.

8

Hello Simon, the documentation does specify that Yast Online update can be used to perform the updates with manually update repositories. What am I not understanding?

Run an Online Update. Make sure the currently installed version has the latest patches installed. Run an Online Update prior to the Online Migration. When using a graphical interface, start the YaST Online Update or the updater applet. On the command line, run the following commands (the last command needs to be run twice): 
The current patches for SUSE® Linux Enterprise Server are available from an update software repository. If you have registered your product during the installation, an update repository is already configured. If you have not registered SUSE Linux Enterprise Server, you can do so by running Software > Online Update Configuration in YaST and start Advanced > Register for Support and Get Update Repository. Alternatively, you can manually add an update repository from a source you trust. To add or remove repositories, start the Repository Manager with Software > Software Repositories in YaST.