Comment # 7 on bug 1189590 from Fabian Vogt

What I noticed is that sometimes it uses /var/cache/zypp/solv/openSUSE-1-0/solv
and sometimes /mnt/var/cache/zypp/solv/openSUSE-1-0/solv.

This looks odd too, and probably reinforces comment 5:

2021-08-19 09:56:37 <1> install(3874) [Pkg] Source_Load.cc(SourceLoadImpl):452
Resolvables from 'openSUSE-1-0' are already present, not loading
2021-08-19 09:56:37 <1> install(3874) [Pkg]
Source_Resolvables.cc(LoadResolvablesFrom):67 Loading resolvables from
'openSUSE-1-0', pool size at start: 5936
2021-08-19 09:56:37 <1> install(3874) [zypp] Repository.cc(eraseFromPool):300
sat::repo(openSUSE-1-0){prio -99.2, size 3773} removed from pool
2021-08-19 09:56:37 <1> install(3874) [zypp::satpool] PoolImpl.cc(setDirty):253
_deleteRepo openSUSE-1-0
2021-08-19 09:56:37 <1> install(3874) [zypp::satpool] PoolImpl.cc(setDirty):253
_createRepo openSUSE-1-0
2021-08-19 09:56:37 <1> install(3874) [zypp::satpool] PoolImpl.cc(setDirty):253
_addSolv openSUSE-1-0

It probably gets confused because the installation medium results in a repo
called "openSUSE-1-0" and the to be upgraded system also contains
/mnt/etc/zypp/repos.d/openSUSE-1-0.repo.

This would explain why it only causes issues in staging, where the version
number is always "1-0".

I did some tests with different upgrade system repos, with the repo removed and
renamed. After renaming, YaST actually proposes to remove it for the upgrade.

openSUSE-1-0: 3/3 failures (wrong actions in overview)
None: 2/2 success
openSUSE-2-0: 2/2 success