Failure in browser_ui/5_package/maven_gradle_repository_spec.rb |Package Maven Repository with Gradle authentication_token_type: :ci_job_token, maven_header_name: "Job-Token" pushes and pulls a maven package via gradle using ci_job_token

Full description

Package Maven Repository with Gradle publishes a maven package via gradle

File path

./qa/specs/features/browser_ui/5_package/maven_gradle_repository_spec.rb

Stack trace

Failure/Error: expect(job).to be_successful(timeout: 800)
  expected `QA::Page::Project::Job::Show.successful?({:timeout=>800})` to return true, got false

First happened in https://gitlab.com/gitlab-org/gitlab-qa-mirror/-/jobs/1371720539.

added QA Quality failureinvestigating found:main priority2 test labels

marked this issue as related to gitlab-org/quality/testcases#1074 (closed)

Seeing this failure in staging-orchestrated https://ops.gitlab.net/gitlab-org/gitlab-qa/-/jobs/4358051

changed the description

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

/cc @svistas

assigned to @svistas

changed milestone to %14.2

The pipeline failures (which include all package managers) are something related to the runner startup, to pull the runner helper image

Pulling docker image registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:x86_64-c1edb478 ...
8WARNING: Failed to pull image with policy "always": Error response from daemon: manifest for registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:x86_64-c1edb478 not found: manifest unknown: manifest unknown (manager.go:205:0s)
10ERROR: Job failed (system failure): failed to pull image "registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:x86_64-c1edb478" with specified policies [always]: Error response from daemon: manifest for registry.gitlab.com/gitlab-org/gitlab-runner/gitlab-runner-helper:x86_64-c1edb478 not found: manifest unknown: manifest unknown (manager.go:205:0s) 

the above screenshot points to a failure where the runtime configurations to build the package are not resolved. I was not able to reproduce this (screenshot) failure against found:main .

I suspect the failures in the pipeline are related to the incident that has been resolved

removed failureinvestigating label

added failuretest-environment label

closed

reopened

Reopening due to failure in MR https://gitlab.com/gitlab-org/gitlab-qa-mirror/-/jobs/1445566314.

The failure is similar

1) Package Maven Repository with Gradle authentication_token_type: :ci_job_token, maven_header_name: "Job-Token" pushes and pulls a maven package via gradle using ci_job_token
     Failure/Error: expect(job).to be_successful(timeout: 800)
       expected `QA::Page::Project::Job::Show.successful?({:timeout=>800})` to return true, got false

but for a different reason this time

cc @svistas , I have only seen this first hand in an MR, but I figured I should log it here for the record.

Seeing this again on staging https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/4728406

mentioned in commit 92119535

unassigned @svistas

changed milestone to %Backlog

removed priority2 label

added devopspackage grouppackage registry labels

added [deprecated] Accepting merge requests label

added sectionops label

mentioned in issue gitlab-org/quality/triage-reports#3994 (closed)

added Category:Package Registry label

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

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

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

Seeing this on Staging https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/4819429

https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/4822189

https://ops.gitlab.net/gitlab-org/quality/staging/-/jobs/4828956

cc @svistas

changed the title since this is happnening specifically with the Job Token. Ran locally and it passes with 3 different methods of authentication. The problem seems to happen after the package is published and when it is consumed by another project. Running it against staging to see if I can reproduce it.

reproduced the error in staging consistently and got

37Execution failed for task ':startScripts'.
38> Could not resolve all files for configuration ':runtimeClasspath'.
39   > Could not find com.gitlab.qa:maven_gradle:1.3.7.
40     Searched in the following locations:
41       - https://jcenter.bintray.com/com/gitlab/qa/maven_gradle/1.3.7/maven_gradle-1.3.7.pom
42       - https://staging.gitlab.com:443/api/v4/projects/6255437/packages/maven/com/gitlab/qa/maven_gradle/1.3.7/maven_gradle-1.3.7.pom
43     Required by:
44         project :

fixed after turning off the FF closing the issue. Context: https://gitlab.slack.com/archives/CB3LSMEJV/p1631282184099900

For completeness, here are the technical details: #332272 (comment 674786721)

changed title from Failure in browser_ui/5_package/maven_gradle_repository_spec.rb | Package Maven Repository with Gradle publishes a maven package via gradle to Failure in browser_ui/5_package/maven_gradle_repository_spec.rb |Package Maven Repository with Gradle authentication_token_type: :ci_job_token, maven_header_name: "Job-Token" pushes and pulls a maven package via gradle using ci_job_token

mentioned in issue #332272 (closed)

closed

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

Reopening as this happened on staging-orchestrated today: https://ops.gitlab.net/gitlab-org/gitlab-qa/-/jobs/4885305

@sliaquat could you please check if this is still happening today? We have deployed a change in the database that disables job token scope by default in project's settings for new projects.

I've also enabled the feature flag that would allow users to opt-in if they want to.

@fabiopitino Can't say as the test is currently failing and in quarantine due to #341209 (closed)

We'll need to wait until that issue is fixed to confirm this.

/cc @svistas

@fabiopitino running against staging, the latest fix is currently passing

reopened

mentioned in issue #343863 (closed)

closed