Error 403 when sending logs about job not launched
I got a report today of a 403 (Forbidden) error, and actually what happened is:
Traceback (most recent call last):
File "/home/paas-runner/paas-runner-venv/lib/python3.9/site-packages/heptapod_runner/paas_dispatcher.py", line 393, in launch_job
if not runner.job_wait_trace(
File "/home/paas-runner/paas-runner-venv/lib/python3.9/site-packages/heptapod_runner/runner.py", line 405, in job_wait_trace
raise JobLaunchTimeout(job_handle, timeout)
and the 403 error is in the error treatment:
File "/home/paas-runner/paas-runner-venv/lib/python3.9/site-packages/heptapod_runner/runner.py", line 359, in job_append_trace
target=lambda: self.launch_job(job_handle, job_data))
File "/home/paas-runner/paas-runner-venv/lib/python3.9/site-packages/heptapod_runner/paas_dispatcher.py", line 405, in launch_job
new_range = self.gl_job_send_trace(
File "/home/paas-runner/paas-runner-venv/lib/python3.9/site-packages/heptapod_runner/runner.py", line 337, in gl_job_send_trace
runner.job_append_trace(
File "/home/paas-runner/paas-runner-venv/lib/python3.9/site-packages/heptapod_runner/runner.py", line 337, in gl_job_send_trace
raise GitLabUnexpectedError(status_code=resp.status_code,
It is possible that the job was already considered to be failed by the coordinator. In any case, this is too much log pollution, and it diverts investigation from the orginal cause.