sameersbn / sameersbn/docker-gitlab
error in trace.json after upgrading to 11.5.0
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
hello I have a weird behavior after upgrading from 11.1.0 to 11.5.0.
when and after running a job I cannot see any details on why the job failed it appears to be a problem with:
https://mygitlab.com/PlayGround/dispatch/-/jobs/93901/trace.json?state=
it returns 500
but when I try the same URL with a job that was built before the upgrade it works.
Gitlab - 11.5.0 (b7b1e8ec)
Gitlab runners - 11.5.0
postgresql - sameersbn/postgresql:10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the jobs/93901/trace.json request on GitLab 11.5.0 after a job runs, then compare it with a job created before the upgrade and review the listed PostgreSQL setup. Done means failed-job details are available and the trace.json endpoint no longer returns HTTP 500.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgresql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100