Project

General

Profile

Actions
Copy link

action #111359

closed

test fails in podman_3rd_party_images

Added by ph03nix about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
jlausuch
Target version:
-
Start date:
2022-05-20
Due date:
% Done:

0%

Estimated time:
Tags:
bug

Description

Observation

The used image registry.access.redhat.com/ubi9-beta/ubi in podman_3rd_party_images does not exist anymore, so all calls using this repository are failing:

# podman pull registry.access.redhat.com/ubi9-beta/ubi
Trying to pull registry.access.redhat.com/ubi9-beta/ubi:latest...
Error: initializing source docker://registry.access.redhat.com/ubi9-beta/ubi:latest: reading manifest latest in registry.access.redhat.com/ubi9-beta/ubi: StatusCode: 404, Not found

This causes all test runs with podman_3rd_party_images to fail, e.g. podman_3rd_party_images

Files

ubi.png (28.2 KB) ubi.png jlausuch, 2022-05-20 07:48

Related issues 1 (0 open — 1 closed)

Has duplicate openQA Tests - action #111371: docker: redhat ubi9 not foundRejected2022-05-20

Actions
Actions
Copy link
 #1

Updated by jlausuch about 2 years ago

According to the documentation, the image should exist, nothing has changed.
https://catalog.redhat.com/software/containers/ubi9-beta/ubi/60a6ea70f13ea7781b9fd615?container-tabs=gti

I guess this is a temporal failure of RH Base image in their registry. Not sure what to do, wait or soft-fail...

Actions
Copy link
 #2

Updated by jlausuch about 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to jlausuch
Actions
Copy link
 #3

Updated by ph03nix about 2 years ago

Actions
Copy link
 #4

Updated by jlausuch about 2 years ago

The funny fact is that the documentation still points to beta images:

However, the images can't be pulled. The beta flag should be removed:

$ podman pull registry.access.redhat.com/ubi9/ubi:latest
Trying to pull registry.access.redhat.com/ubi9/ubi:latest...
Getting image source signatures
Copying blob 2c9b1d3d1a0a done  
Copying blob f95ee31bf3b7 done  
Copying config 46720ac964 done  
Writing manifest to image destination
Storing signatures
46720ac964ac0e5fb23c8594797c3f7bb19c5a82c4734957f8991e94c30bd9f8

$ podman pull registry.access.redhat.com/ubi9/ubi-minimal
Trying to pull registry.access.redhat.com/ubi9/ubi-minimal:latest...
Getting image source signatures
Copying blob f9d62bce50f7 done  
Copying blob 2e1b1dfebe63 done  
Copying config 8b9dbc6a97 done  
Writing manifest to image destination
Storing signatures
8b9dbc6a97658cf67c13b3194d806560bc689eb677a0c7b2101d4a9f355b7331

$ podman pull registry.access.redhat.com/ubi9/ubi-micro
Trying to pull registry.access.redhat.com/ubi9/ubi-micro:latest...
Getting image source signatures
Copying blob c0c5781d2b01 done  
Copying blob 4f4fb700ef54 done  
Copying config 52122e9e5c done  
Writing manifest to image destination
Storing signatures
52122e9e5c454b1ebeb43ac6f42238933ad086fe6745ad25408132cd3597cbd4

$ podman pull registry.access.redhat.com/ubi9/ubi-init
Trying to pull registry.access.redhat.com/ubi9/ubi-init:latest...
Getting image source signatures
Copying blob 2c9b1d3d1a0a skipped: already exists  
Copying blob f95ee31bf3b7 skipped: already exists  
Copying blob 786eccf57cca done  
Copying config 632d4802e2 done  
Writing manifest to image destination
Storing signatures
632d4802e2e963d543355e6d2eb822cf39fd3f03e2798c7f82c139e145ddaa7e
Actions
Copy link
 #5

Updated by ph03nix about 2 years ago

podman pull registry.access.redhat.com/ubi9/ubi:latest works, so we probably just need to remote the beta from the link there.

Weirdly ubi9-beta/ubi is still advertised in https://catalog.redhat.com

Actions
Copy link
 #7

Updated by jlausuch about 2 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #8

Updated by dimstar about 2 years ago

  • Status changed from Feedback to Workable

jlausuch wrote:

There you go https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14936

The error changed: ubi9 containers are not compatible to o3:
https://openqa.opensuse.org/tests/2358608#step/podman_3rd_party_images/467

Fatal glibc error: CPU does not support x86-64-v2

Actions
Copy link
 #9

Updated by jlausuch about 2 years ago

dimstar wrote:

jlausuch wrote:

There you go https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14936

The error changed: ubi9 containers are not compatible to o3:
https://openqa.opensuse.org/tests/2358608#step/podman_3rd_party_images/467

Fatal glibc error: CPU does not support x86-64-v2

Whaaaaat? Ok... I might disable them for now and further investigate...

Actions
Copy link
 #10

Updated by jlausuch about 2 years ago

Agree to disable the images from now: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14939
We will come back with proper fix next week.

The needed cpu flags that proof that x86_64-v2 is supported are:
cx16 lahf popcnt sse4_1 sse4_2 ssse3e
but it might be safer to just do QEMUCPU=host.

Actions
Copy link
 #11

Updated by jlausuch about 2 years ago

  • Priority changed from Urgent to Normal

Lowering prio, as main issue is solved by disabling the images.

Actions
Copy link
 #13

Updated by jlausuch about 2 years ago

  • Tags set to bug
  • Project changed from 193 to Containers
  • Status changed from Workable to In Progress
Actions
Copy link
 #14

Updated by jlausuch about 2 years ago

This makes a fair condition to run the image or not depending on the cpu flags:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14945

If we want to run this image in regular openQA jobs, we will need to set QEMUCPU=host

Actions
Copy link
 #15

Updated by jlausuch about 2 years ago

  • Status changed from In Progress to Resolved

Problem solved with that PR. Latest SLE maintenance jobs are green again.
However, this means we are not running ubi9 images as we use cpu=qemu64...
We need to add QEMUCPU=host to our container tests.

Actions
Copy link

Also available in: Atom PDF