Hi,
first of all, sorry, but I’m absolutely no openSUSE expert. I manage a openSUSE VM which I got from a former employee. Now I wanted to upgrade it from 15.2 to 15.3 but I get a upgrade conflict which I’m not able to resolve. Here are some details. If i missed some important infos, please ask me and I’m happy to provide more details.
# zypper --releasever=15.3 lr -u
Warning: Enforced setting: $releasever=15.3
Repository priorities in effect: (See 'zypper lr -P' for details)
40 (raised priority) : 2 repositories
50 (raised priority) : 1 repository
55 (raised priority) : 1 repository
99 (default priority) : 1 repository
# | Alias | Name | Enabled | GPG Check | Refresh | URI
--+----------------+----------------+---------+-----------+---------+------------------------------------------------------------------
1 | non-oss | non-oss | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/
2 | oss | oss | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.3/repo/oss/
3 | packman | packman | Yes | (r ) Yes | Yes | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Leap_15.3/
4 | update-non-oss | update-non-oss | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/non-oss/
5 | update-oss | update-oss | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/oss/
#
# zypper --releasever=15.3 ref
Warning: Enforced setting: $releasever=15.3
Retrieving repository 'non-oss' metadata ----------------------------------------------------------------------------------------------------------------\]
Note: Received 2 new package signing keys from repository non-oss:
Those additional keys are usually used to sign packages shipped by the repository. In order to
validate those packages upon download and installation the new keys will be imported into the rpm
database.
New:
Key Fingerprint: 637B 32FF 3D83 F07A 7AE1 C40A 9C21 4D40 6517 6565
Key Name: openSUSE:Backports OBS Project <openSUSE:Backports@build.opensuse.org>
Key Algorithm: RSA 2048
Key Created: Wed Oct 2 15:17:53 2019
Key Expires: Fri Dec 10 14:17:53 2021 (EXPIRED)
Rpm Name: gpg-pubkey-65176565-5d94a381
New:
Key Fingerprint: FEAB 5025 39D8 46DB 2C09 61CA 70AF 9E81 39DB 7C82
Key Name: SuSE Package Signing Key <build@suse.de>
Key Algorithm: RSA 2048
Key Created: Mon Sep 21 10:21:47 2020
Key Expires: Fri Sep 20 10:21:47 2024
Rpm Name: gpg-pubkey-39db7c82-5f68629b
The repository metadata introducing the new keys have been signed and validated by the trusted
key:
Repository: non-oss
Key Fingerprint: 22C0 7BA5 3417 8CD0 2EFE 22AA B88B 2FD4 3DBD C284
Key Name: openSUSE Project Signing Key <opensuse@opensuse.org>
Key Algorithm: RSA 2048
Key Created: Mon May 5 10:37:40 2014
Key Expires: Thu May 2 10:37:40 2024
Rpm Name: gpg-pubkey-3dbdc284-53674dd4
Retrieving repository 'non-oss' metadata .............................................................................................................[done]
Building repository 'non-oss' cache ..................................................................................................................[done]
Retrieving repository 'oss' metadata .................................................................................................................[done]
Building repository 'oss' cache ......................................................................................................................[done]
Retrieving repository 'packman' metadata .............................................................................................................[done]
Building repository 'packman' cache ..................................................................................................................[done]
Retrieving repository 'update-non-oss' metadata ......................................................................................................[done]
Building repository 'update-non-oss' cache ...........................................................................................................[done]
Retrieving repository 'update-oss' metadata ..........................................................................................................[done]
Building repository 'update-oss' cache ...............................................................................................................[done]
All repositories have been refreshed.
Then proceeding with the upgrade:
zypper --releasever=15.3 dup --allow-vendor-change
.....
.....
.....
The following NEW product is going to be installed:
"openSUSE Leap 15.3"
The following 30 packages are going to be REMOVED:
gtk2-engine-murrine-32bit hardlink kernel-default-5.3.18-lp152.98.1 kernel-default-5.3.18-lp152.106.1 kernel-firmware kmod-compat libattica0_4
libdbusmenu-qt2 libevtlog-3_26-0 libgnomecups-1_0-1-32bit libgnutls-dane0 libiniparser0-32bit libndr0 libndr0-32bit libphonon4 libqt4 libqt4-qt3support
libqt4-sql libqt4-sql-sqlite libqt4-x11 libyui-ncurses-pkg11 libyui-qt-pkg11 phonon-backend-gstreamer python-qt4-utils python2-pysmbc python2-qt4
python3-pycairo python3-pysmbc systemd-bash-completion tclplug-32bit
The following product is going to be REMOVED:
"openSUSE Leap 15.2"
The following package requires a system reboot:
kernel-default-5.3.18-59.10.1
4487 packages to upgrade, 386 to downgrade, 96 new, 30 to remove, 4531 to change vendor.
Overall download size: 2.55 GiB. Already cached: 0 B. After the operation, 601.7 MiB will be freed.
Note: System reboot required.
Continue? [y/n/v/...? shows all options] (y): y
Do you agree with the terms of the license? [yes/no] (no): yes
....
....
....
After downloading all the packages it checks for conflicts and reports a conflict:
Checking for file conflicts: ........................................................................................................................[error]
Detected 1 file conflict:
File /usr/lib64/libhandle.so.1.0.3
from install of
xfsprogs-4.15.0-4.27.1.x86_64 (oss)
conflicts with file from package
libhandle1-4.15.0-lp152.12.6.1.x86_64 (@System)
File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content.
No I stuck on this conflict which I can’t resolve. I tried several things, but all failed. Prior to upgrading again (after I restored the VM from the snapshot before even trying to upgrade) I tried do remove libhandle and/or xfsprogs but both ends in the conflict again (so even if I remove libhandle before upgrading + reboot the machine, the conflict appears, thus I seems that the upgrade process is installing both packages anyway resulting in the conflict no matter what). Those xfsprogs / libhandle are installed prior to the upgrade:
# rpm -qa | grep -i xfsprogs
xfsprogs-4.15.0-lp152.12.6.1.x86_64
#
# rpm -qa | grep -i libhandle
libhandle1-4.15.0-lp152.12.6.1.x86_64
Thus the xfsprogs version seems to be different than it tries to upgrade.
If I abort the upgrade after I get the notification about the conflict and then remove libhandle or xfsprogs and restart the upgrade (with the same command above), then the conflict is gone but the system reboots while installing systemd:
(1222/4991) Installing: aaa_base-84.87+git20180409.04c9dae-3.45.1.x86_64 .....................[done]|
Additional rpm output:
Updating /etc/sysconfig/language ...
Updating /etc/sysconfig/proxy ...
Updating /etc/sysconfig/windowmanager ...
(1223/4991) Removing kernel-default-5.3.18-lp152.98.1.x86_64 .................................[done]|
(1224/4991) Installing: suse-module-tools-15.3.6-1.1.x86_64 ..................................[done]|
(1225/4991) Installing: kmod-28-2.1.x86_64 ...................................................[done]|
(1226/4991) Installing: systemd-246.13-5.1.x86_64 .........................................<100%>-]Timeout, server
After that the system is in a boot loop. Its pretty interesting that it reboots while installing systemd. First I thought that the system disk might be full, but prior to upgrading I checked the available free space:
# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 3.9G 1.3M 3.9G 1% /run
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/sda1 64G 26G 39G 41% /
Thus it should be enough space left, so I don’t know why it is rebooting while installing systemd. But overall I don’t know if this is correlated with the conflict and how to resolve the conflict properly. Thus any help is really appreciated! Thx in advance!