Project

General

Profile

Actions

action #107806

closed

docker build fails - No provider of 'apache2' found due to container-suseconnect-zypp failure.

Added by jlausuch over 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
2022-03-03
Due date:
% Done:

0%

Estimated time:
Tags:

Description

Observation

openQA test in scenario sle-15-Server-DVD-Updates-x86_64-docker_tests@64bit fails in
image_docker

I noticed it fails from time to time, a restart of the job normally helps, but it's worth to invest a bit in improving the code to handle this failure.
Maybe a script_retry could help, but I guess we need to cleanup the half-created container before retrying...

# docker build -f /var/tmp/containerapp/BuildTest/Dockerfile -t myapp /var/tmp/containerapp/BuildTest; echo Ob1IB-$?-
Sending build context to Docker daemon  3.072kB


Step 1/7 : FROM zypper_docker_derived
 ---> 124e3f7c0f8a
Step 2/7 : RUN zypper -n in apache2 && zypper clean -a
 ---> Running in ac4289e3abc0
Refreshing service 'container-suseconnect-zypp'.
Removing repository 'SLES12-SP4-Debuginfo-Pool for sle-12-x86_64' [...done]
Removing repository 'SLES12-SP4-Debuginfo-Updates for sle-12-x86_64' [...done]
Removing repository 'SLES12-SP4-Pool for sle-12-x86_64' [...done]
Removing repository 'SLES12-SP4-Source-Pool for sle-12-x86_64' [...done]
Removing repository 'SLES12-SP4-Updates for sle-12-x86_64' [...done]
Problem retrieving the repository index file for service 'container-suseconnect-zypp':
[container-suseconnect-zypp|file:/usr/lib/zypp/plugins/services/container-suseconnect-zypp] 
Warning: Skipping service 'container-suseconnect-zypp' because of the above error.
Loading repository data...
Warning: No repositories defined. Operating only with the installed resolvables. Nothing can be installed.
Reading installed packages...
'apache2' not found in package names. Trying capabilities.
No provider of 'apache2' found.
The command '/bin/sh -c zypper -n in apache2 && zypper clean -a' returned a non-zero code: 104
Ob1IB-104-

Test suite description

The base test suite is used for job templates defined in YAML documents. It has no settings of its own.

Reproducible

Fails since (at least) Build 20220303-1 (current job)

Expected result

Last good: 20220302-1 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 1 (1 open0 closed)

Related to openQA Tests - action #107062: Multiple failures due to network issuesFeedbackjstehlik2021-09-27

Actions
Actions #1

Updated by jlausuch over 2 years ago

Similar:
https://openqa.suse.de/tests/8263328#step/image_docker/194

# docker build -f /var/tmp/containerapp/BuildTest/Dockerfile -t myapp /var/tmp/containerapp/BuildTest; echo dss5l-$?-
Sending build context to Docker daemon  3.584kB


Step 1/7 : FROM registry.suse.com/suse/sles12sp5
 ---> 2f24e007b273
Step 2/7 : RUN zypper -n in apache2 && zypper clean -a
 ---> Running in c06d9df77fac
Refreshing service 'container-suseconnect-zypp'.
Adding repository 'SLES12-SP5-Debuginfo-Pool for sle-12-aarch64' [......done]
Adding repository 'SLES12-SP5-Debuginfo-Updates for sle-12-aarch64' [......done]
Adding repository 'SLES12-SP5-Pool for sle-12-aarch64' [......done]
Adding repository 'SLES12-SP5-Source-Pool for sle-12-aarch64' [......done]
Adding repository 'SLES12-SP5-Updates for sle-12-aarch64' [......done]
Building repository 'SLES12-SP5-Pool for sle-12-aarch64' cache [....done]
Retrieving repository 'SLES12-SP5-Updates for sle-12-aarch64' metadata [.Download (curl) error for 'https://updates.suse.com/SUSE/Updates/SLE-SERVER/12-SP5/aarch64/update/repodata/repomd.xml?1d2srOVNIUey17Z1SS1OCSXavb8DSZ_ozbQ6_dl5yAxaxNhDviT0caQcVgLotM6Wnvtujxsd0npdFg6wGsrw8mfWysCOxWhBYXwznCPE9Kla3Q4muDerhsAdJWcNLNSHzOsWUEaisOUeTn3W':
Error code: Connection failed
Error message: Could not resolve host: updates.suse.com
Actions #2

Updated by jlausuch over 2 years ago

  • Related to action #107062: Multiple failures due to network issues added
Actions #3

Updated by jlausuch over 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to jlausuch
Actions #4

Updated by jlausuch over 2 years ago

  • Status changed from In Progress to Feedback
Actions #5

Updated by jlausuch about 2 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF