action #40958

[containers] test fails in docker - ppc64le packages within container not in sync with published repos

Added by michel_mno about 3 years ago. Updated 16 days ago.

Bugs in existing tests
Target version:
Start date:
Due date:
% Done:


Estimated time:


test fails in docker because "zypper in -n curl" is reporting a dependency problem.

seems container previously created with libcurl4-7.61.1-1.1.ppc64le
but curl-7.61.0-3.1.ppc64le needs libcurl4-7.61.0-3.1.ppc64le

I assume this is expected as the way container and oss repo are not generated from same OBS projects.

Note: related code was merged with

my proposal would be to modify the test script to detect the failure
and retry with "zypper in --force-resolution -y -n curl"

Problem: curl-7.61.0-3.1.ppc64le requires libcurl4 = 7.61.0, but this requirement cannot be provided
not installable providers: libcurl4-7.61.0-3.1.ppc64le[repo-oss]
Solution 1: downgrade of libcurl4-7.61.1-1.1.ppc64le to libcurl4-7.61.0-3.1.ppc64le
Solution 2: do not install curl-7.61.0-3.1.ppc64le

Solution 3: break curl-7.61.0-3.1.ppc64le by ignoring some of its dependencies


openQA test in scenario opensuse-Tumbleweed-DVD-ppc64le-docker_image@ppc64le fails in


Fails since (at least) Build 20180903

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest


#1 Updated by michel_mno about 3 years ago

I suggested a bypass with

Another problem I noticed while investigating this issue is that script_output() method seems to not return in case of failure, that means the next line testing $output is useless:

#2 Updated by okurz almost 3 years ago

  • Subject changed from test fails in docker to [containers] test fails in docker - ppc64le packages within container not in sync with published repos
  • Assignee set to favogt

favogt haven't you discussed this lately with ggardet for the corresponding problem on aarch64? Is there a bug about that or another ticket which we can link?

#4 Updated by okurz 16 days ago

  • Priority changed from Normal to Low

This ticket was set to "Normal" priority but was not updated within 730 days which is 2 times the period of the SLO for "Normal" tickets (365 days) as described on . The ticket will be set to the next lower priority of "Low".

Also available in: Atom PDF