Replace this template with your information
Describe your question in as much detail as possible:
-
What are you seeing, and how does that differ from what you expect to see?
We are observing GitLab Pipeline are being stucked in some stage and passing misleading information on UI. For instance, if the Pipeline has failed still in UI it reflects as running and on drill down to job. We find that JOB is has failed or next stage is not triggered.
We expect that if one stage has passed then next stage shall get triggered or if the job has failed pipeline status should also reflect as fail.
-
Consider including screenshots, error messages, and/or other helpful visuals
-
What version are you on? Are you using self-managed or GitLab.com?
We are using Gitlab version 13.11ee community edition. Yes, we are using Self-managed GitLab.com .- GitLab (Hint:
/help
): - Runner (Hint:
/admin/runners
):
- GitLab (Hint:
-
Add the CI configuration from
.gitlab-ci.yml
and other configuration if relevant (e.g. docker-compose.yml) -
What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?
We saw 100% disk space utilization and memory issue. So, increased the EC2 instance to m5.2xlarge and freed disk space utilization.
We restarted the gitlab runner and EC2 machine on which runner is installed. Checked application.log and sidekiq.log did not found any error instance.
Thanks for taking the time to be thorough in your request, it really helps!