Upgrade from 15.2 to 15.3 fails to update /etc/products.d/baseproduct

English Install/Boot/Login
#1

Just upgraded a VM from 15.2 to 15.3.

Following on from a previous thread I edited the repso to use $releasever instead of being hardcoded.

The upgrade went like a charm (mostly!) with “zypper --releasever=15.3 dup --allow-vendor-change”.

However after that I kept getting errors when executing commands like “zypper up”.

Progress:~ # zypper up
Warning: The /etc/products.d/baseproduct symlink is dangling or missing!
The link must point to your core products .prod file in /etc/products.d.

Retrieving repository 'Main Repository (NON-OSS)' metadata ..............................................................[done]
Building repository 'Main Repository (NON-OSS)' cache ...................................................................[done]
Retrieving repository 'Main Repository (OSS)' metadata ..................................................................[done]
Building repository 'Main Repository (OSS)' cache .......................................................................[done]
Retrieving repository 'packman' metadata ...............................................................................[error]
Repository 'packman' is invalid.
[packman|http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_/] Valid metadata not found at specified URL
History:
 - [packman|http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_/] Repository type can't be determined.


Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'packman' because of the above error.
Retrieving repository 'openSUSE-Leap--Update' metadata ..................................................................[done]
Building repository 'openSUSE-Leap--Update' cache .......................................................................[done]
Retrieving repository 'openSUSE-Leap--Update-Non-Oss' metadata ..........................................................[done]
Building repository 'openSUSE-Leap--Update-Non-Oss' cache ...............................................................[done]
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...
Nothing to do.
Progress:~ #

It looked like the $releasever substitution was not happening. Not sure how it found any repositories but maybe there is a non release specific default.

Traced it down to the /etc/products.d/baseproduct symlink being broken. OK, I actually read the first warning!

Progress:/etc/products.d # ls -la
total 28
drwxr-xr-x   2 root root  4096 Mar  5 17:52 .
drwxr-xr-x 163 root root 12288 Mar  7 11:33 ..
-rw-r--r--   1 root root  1874 Mar  1 11:35 Leap-Addon-NonOss.prod
-rw-r--r--   1 root root  4301 Mar  1 11:35 Leap.prod
lrwxrwxrwx   1 root root    13 Jul 30  2017 baseproduct -> openSUSE.prod
Progress:/etc/products.d #

There is no file openSUSE.prod. Fixed it and tested it as follows.

Progress:/etc/products.d # rm baseproduct
Progress:/etc/products.d # ln -s Leap.prod baseproduct 
Progress:/etc/products.d # ls -al
total 28
drwxr-xr-x   2 root root  4096 Mar  7 11:48 .
drwxr-xr-x 163 root root 12288 Mar  7 11:33 ..
-rw-r--r--   1 root root  1874 Mar  1 11:35 Leap-Addon-NonOss.prod
-rw-r--r--   1 root root  4301 Mar  1 11:35 Leap.prod
lrwxrwxrwx   1 root root     9 Mar  7 11:48 baseproduct -> Leap.prod
Progress:/etc/products.d # zypper up
Retrieving repository 'Main Repository (NON-OSS)' metadata ..............................................................[done]
Building repository 'Main Repository (NON-OSS)' cache ...................................................................[done]
Retrieving repository 'Main Repository (OSS)' metadata ..................................................................[done]
Building repository 'Main Repository (OSS)' cache .......................................................................[done]
Retrieving repository 'openSUSE-Leap-15.3-Update' metadata ..............................................................[done]
Building repository 'openSUSE-Leap-15.3-Update' cache ...................................................................[done]
Retrieving repository 'openSUSE-Leap-15.3-Update-Non-Oss' metadata ......................................................[done]
Building repository 'openSUSE-Leap-15.3-Update-Non-Oss' cache ...........................................................[done]
Loading repository data...
Reading installed packages...
Nothing to do.

Are others encountering this too?

#2

I am not sure many others will have this. Most 15.3 testers will just install it and not upgrade. I guess that testing the upgrade procedure will be one of the last things done. But I also assume that developers like it to hear from your experience when you file a bug report.

#3

Post:

zypper se -s openSUSE-release

And if it is installed:

rpm -ql openSUSE-release | grep -i etc

This is on Leap 15.2:

rpm -ql openSUSE-release | grep -i etc
/etc/YaST2
/etc/YaST2/control.xml
/etc/issue
/etc/motd
/etc/os-release
/etc/products.d
/etc/products.d/baseproduct
/etc/products.d/openSUSE.prod
#4

Maybe you should fill a bugreport:

rpm -qlp https://download.opensuse.org/distribution/leap/15.3/repo/oss/x86_64/openSUSE-release-15.3-lp153.77.1.x86_64.rpm | grep -i etc
/etc/YaST2
/etc/YaST2/control.xml
/etc/issue
/etc/motd
/etc/os-release
/etc/products.d
/etc/products.d/Leap.prod
/etc/products.d/baseproduct
/etc/zypp/vendors.d/00-openSUSE.conf
#5

Fine, I’ll do a report, just don’t like filing one if I have made a schoolboy error :wink:

#6

There’s already a bug report about this. I think it lists the problem as solved, but that means it will be solved after the next update.

I have not tried an online upgrade myself.

#7

A short summary how my upgrade went including the answer to your question.
Early February I upgraded 15.2 to 15.3 alpha almost exactly like you with with
“zypper --releasever=15.3 dup --allow-downgrade --allow-vendor-change”.
Zypper was complaining about a missing gpg key for backport packages and the YaST software module about /etc/products.d/baseproduct being a dangling symlink. After importing the missing key into the rpm database and bending the symlink to /etc/products.d/Leap.prod everything was fine.
The reason for upgrading were two annoying bugs in Leap 15.2 on my old HP Elitebook 8570p:
The keyboard would not work after resume from suspend, a well known bug in the atkbd kernel module, and my Plasma desktop switched many times back to default background and icon arrangement, also a known bug.
Leap 15.3 is still at kernel 5.3 and Plasma 5.18, but both bugs seem to be gone. Obviously there has been some backporting. Systemd has been updated to version 246 and systemd-resolved is finally available, although the packages systemd-network and nss-resolve are not part of the default installation.

Because of infrequent repo updates I have some security concerns. Now that beta has been released, I hope this will change. In the meantime I use Debian testing with newer kernel and Plasma versions.

#8

For a while, the install DVD was being updated but the repos were not being updated. As best I can tell, they have solved that problem. So it looks as if the repos will now be up to date with the beta DVD installer.

It is typical for beta releases to be updated less often. Getting security fixes out quickly is probably not seen as important for a beta release. The fixes can wait until the next version has passed all openQA test for the full distribution.

#9

If the repo updates of Leap 15.3 beta were not as frequent as those of Tumbleweed, I could live with it. But once a week should be doable.

#10

This is a testing environment. Either you live with it, or go for one of the supported versions. :wink:

#11

I can live with it. But I also think a lot more people would be willing to test the beta by using it regularly, if they had the impression to get a minimum of security updates.

#12

To me it is clear not to have any important data on a test system when testing the operating system.

#13

Leap 15.3 is Beta.

All bugs and security fixes will going to the versions in the OSS Repo, because this will be the versions when Leap 15.3 will be delivered.
How often the OSS repo will be created new I do not know.

After the release day new bugfixes and security fixes will going into the Update Repo because the OSS Repo will not be touched for the release time.

So the update Repo is created but will only be used after release.