[temurin-compliance] jenkins server giving 502 Bad Gateway errors
Summary
Symptoms similar to #2001 (closed) from last week - system is giving "502 Bad Gateway" errors around 50% of the time so service is degraded (Although it was 504 errors I was seeing last week, but it's making the service hard to use.
Priority
-
Urgent -
High -
Medium -
Low
Severity
-
Blocker -
Major -
Normal -
Low
Impact
(What is the impact of this issue? Is it blocking a release? Are there any time constraints?, for example: "We have a release tomorrow")
Required for remaining releases on some platforms - since the system is "sometimes" responsive we can continue albeit slowly.
Edited by Frederic Gurr