Uh oh!
There was an error while loading. Please reload this page.
fix: gracefully handle 404 from worker log server for historical retry attempts - #63002
Conversation
kalluripradeep
commented
Mar 6, 2026
@eladkal — backport PR for v2-11-test as requested. |
Uh oh!
There was an error while loading. Please reload this page.
eladkal
commented
Mar 6, 2026
@kalluripradeep can you verify if the failures in |
kalluripradeep
commented
Mar 6, 2026
@eladkal — confirmed these failures are unrelated to this PR. The failing tests are This PR only modifies |
Uh oh!
There was an error while loading. Please reload this page.
potiuk
commented
Mar 7, 2026
Yes. That was a problem with Celery Provider 3.17.0 #63043 |
Backport of #62475 to v2-11-test.
Original PR: #62475
What changed
Added 404 handling in
_read_from_logs_serverinfile_task_handler.pywith a local filesystem fallback and a clear message when logs aren't accessible.How I fixed it
Added an
elif response.status_code == 404branch that:_read_from_local— covers cases where logs are on a shared driveFixes#62372