Skip to content

License check API responds with HTTP status 502 (Bad Gateway)

Summary

JGit builds are failing due to the license check API responding with HTTP status 502 (Bad Gateway)

Steps to reproduce

retrigger the JGit build https://ci.eclipse.org/jgit/job/stable/job/jgit-stable.gerrit/4694

What is the current bug behavior?

Requests to license check API fail with HTTP status 502 (Bad Gateway).

What is the expected correct behavior?

License checks should succeed.

Relevant logs and/or screenshots

https://ci.eclipse.org/jgit/job/stable/job/jgit-stable.gerrit/4694/console

...
[INFO] --- license-tool:1.1.0:license-check (license-check) @ org.eclipse.jgit-parent ---
[INFO] Querying Eclipse Foundation for license data for 69 items.
[INFO] HTTP response 502 (Bad Gateway). Trying again...
[INFO] HTTP response 502 (Bad Gateway). Trying again...
[INFO] HTTP response 502 (Bad Gateway). Trying again...
[INFO] HTTP response 502 (Bad Gateway). Trying again...
[INFO] HTTP response 502 (Bad Gateway). Trying again...
[INFO] HTTP response 502 (Bad Gateway). Trying again...
[INFO] HTTP response 502 (Bad Gateway). Trying again...
[INFO] HTTP response 502 (Bad Gateway). Trying again...
[INFO] HTTP response 502 (Bad Gateway). Trying again...
[INFO] HTTP response 502 (Bad Gateway). Trying again...
[ERROR] Error response from the Eclipse Foundation 502
...
[ERROR] Failed to execute goal org.eclipse.dash:license-tool-plugin:1.1.0:license-check (license-check) on project org.eclipse.jgit-parent: Execution license-check of goal org.eclipse.dash:license-tool-plugin:1.1.0:license-check failed: Received an

Priority

  • Urgent
  • High
  • Medium
  • Low

Severity

  • Blocker
  • Major
  • Normal
  • Low

Impact

JGit builds are failing

Edited by Matthias Sohn