Failure in browser_ui/5_package/dependency_proxy_spec.rb | Package Dependency Proxy docker_client_version: docker:19.03.12 pulls an image using the dependency proxy

added QA Quality failureinvestigating found:main priority2 test labels

added automation:ml grouppackage registry labels

This issue was automatically tagged with the label ~"group::package" by TanukiStan, a machine learning classification model, with a probability of 1.

If this label is incorrect, please tag this issue with the correct group label as well as automation:ml wrong to help TanukiStan learn from its mistakes.

This message was generated automatically. You're welcome to improve it.

mentioned in merge request !72711 (merged)

Happening in master

Hi @svistas - do you have any ideas what may be causing this.

Is it perhaps related to #334432 (closed) ?

thanks for the ping here @john.mcdonnell , there is a fix MR for this coming up: !71905 (merged) the issue is that the dependency proxy is trying to connect via HTTPS and the GitLab instance does not have the certificate. The CI script is modified on the fix MR to accommodate this.

cc @balasankarc

Fix: !73825 (merged) closing the issue

changed the description

added sectionops label

mentioned in issue gitlab-org/quality/pipeline-triage#105 (closed)

The changes to the runners as part of gitlab-qa#261 (closed) were made around 25th/26th October 2021, which coincides with when we started to see this issue occur. https://dashboards.quality.gitlab.net/goto/32EZ5SFnz?orgId=1

@balasankarc - might this be related to why we are having issues connecting to a docker registry in these tests?

@john.mcdonnell Can we confirm if this is happening only on jobs run on qa-runner and not on build-trigger-runner-manager-gitlab-org ? If so, then yes - this might be related to the addition of new runner.

We can temporarily pause that runner while we investigate, and have all the jobs processed by build-trigger-runner-manager-gitlab-org if that is the case.

(I did verify we are not running into https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/898 and docker daemon is started with MTU=1460 on the machines spun up by the new runner)

Can we confirm if this is happening only on jobs run on qa-runner and not on build-trigger-runner-manager-gitlab-org

https://gitlab.com/gitlab-org/gitlab-qa-mirror/-/jobs/1718299285 was in build-trigger-runner-manager-gitlab-org. So this doesn't seem related to the new runner.