Description:¶

# zypper -n in -l --force-resolution --solver-focus Update postfix-bdb postfix-bdb-lmdb postfix-devel postfix-ldap postfix-doc postfix postfix-mysql 

Loading repository data...
Reading installed packages...
'postfix' is already installed.
No update candidate for 'postfix-3.5.9-5.9.2.x86_64'. The highest available version is already installed.
Resolving package dependencies...
2 Problems:
Problem: the to be installed postfix-mysql-3.5.9-5.9.2.x86_64 requires 'postfix = 3.5.9', but this requirement cannot be provided
Problem: the to be installed postfix-ldap-3.5.9-5.9.2.x86_64 requires 'postfix = 3.5.9', but this requirement cannot be provided

Problem: the to be installed postfix-mysql-3.5.9-5.9.2.x86_64 requires 'postfix = 3.5.9', but this requirement cannot be provided
  not installable providers: postfix-3.5.9-3.18.x86_64[sle-module-basesystem:15-SP3::pool]
                   postfix-3.5.9-5.3.3.x86_64[sle-module-basesystem:15-SP3::update]
                   postfix-3.5.9-5.6.1.x86_64[sle-module-basesystem:15-SP3::update]
 Solution 1: Following actions will be done:
  do not install postfix-mysql-3.5.9-5.9.2.x86_64
  do not install postfix-devel-3.5.9-5.9.2.x86_64
 Solution 2: do not install postfix-bdb-3.5.9-5.9.2.x86_64
 Solution 3: break postfix-mysql-3.5.9-5.9.2.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): c

I did a quick check, and it might be caused we install postfix and postfix-bdb* at the same time.

We may need to fix our test code or shall we file a bug report?

Observation¶

openQA test in scenario sle-15-SP3-Server-DVD-Incidents-Install-x86_64-qam-incidentinstall@64bit fails in
update_install

Test suite description¶

Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Incident Installation TEST
MAX_JOB_TIME=9000 due to long texlive update

Reproducible¶

Fails since (at least) Build :31975:postfix (current job)

Expected result¶

Last good: :31455:pesign (or more recent)

Further details¶

Always latest result in this scenario: latest