Use GitLab-hosted RHEL image in integration test
What does this MR do?
We've been encountering flaky integration tests for the registry.access.redhat.com/rhel7:7.9-333
image, either because we're getting rate-limited by registry.access.redhat.com
or the server is just unreliable:
2023-12-13T00:49:38.583Z FATAL image scan error: scan error: unable to initialize a scanner: unable to initialize a docker scanner: 4 errors occurred:
* unable to inspect the image (registry.access.redhat.com/rhel7:7.9-333): Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
* containerd socket not found: /run/containerd/containerd.sock
* unable to initialize Podman client: no podman socket found: stat podman/podman.sock: no such file or directory
* Get "https://registry.access.redhat.com/v2/rhel7/manifests/7.9-333": stopped after 10 redirects
This MR uses a GitLab-hosted RHEL image to fix the flaky integration tests.
What are the relevant issue numbers?
N/A
Does this MR meet the acceptance criteria?
-
Changelog trailer added -
Documentation created/updated for GitLab EE, if necessary -
Documentation created/updated for this project, if necessary -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Job definition updated, if necessary -
Conforms to the code review guidelines -
Conforms to the Go guidelines -
Security reports checked/validated by reviewer
Edited by Adam Cohen