Project

General

Profile

Actions

action #40958

open

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

Added by michel_mno almost 6 years ago. Updated about 1 year ago.

Status:
Workable
Priority:
Low
Assignee:
-
Target version:
-
Start date:
2018-09-13
Due date:
% Done:

0%

Estimated time:
Tags:

Description

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 https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4482

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

Observation

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

Reproducible

Fails since (at least) Build 20180903

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by michel_mno almost 6 years ago

I suggested a bypass with https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/5767

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: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4482/commits/b9df3f35ea7dfe98966c2082345521149ce62bc8#diff-d2138a16f3e6eabf5ea87cf82a9e671bR102

Actions #2

Updated by okurz almost 6 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?

Actions #3

Updated by michel_mno over 5 years ago

Actions #4

Updated by okurz almost 3 years 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 https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . The ticket will be set to the next lower priority of "Low".

Actions #5

Updated by jlausuch over 2 years ago

  • Status changed from New to Closed

I just came accross this ticket by chance and I think it's safe to be closed. This issue is not happening now.

Actions #6

Updated by favogt over 2 years ago

  • Status changed from Closed to Workable
  • Assignee deleted (favogt)

Reopening, I think the root cause (invalid test setup) is still there, just masked in an even more invalid way.

When running zypper inside the container under test, then it also needs to use the repos under test, i.e. "repo replacement" must also be done in the container.

Actions #7

Updated by jlausuch over 2 years ago

  • Tags set to bug
  • Project changed from openQA Tests to Containers
  • Category deleted (Bugs in existing tests)
Actions #8

Updated by mloviska about 1 year ago

Actions

Also available in: Atom PDF