Sometimes pipeline status is not automatically updated on Merge Request page
Summary
Sometimes, the pipeline status on Merge Request fails to automatically update. This causes end to end tests that depend on this condition to fail, creates a false negative.
Steps to reproduce
I ran into this issue more often when running test against GDK.
Example: Run this test
bundle exec bin/qa Test::Instance::All http://10.0.0.42:3000 -- qa/specs/features/browser_ui/4_verify/pipeline/merge_mr_when_pipline_is_blocked_spec.rb
The test basically will create a project, launch a runner, commit CI file with 1 manual job, push a merge request and go to this Merge Request page. Here it will wait for pipeline status to change to waiting for manual action
(blocked pipeline).
Example Project
Per pipeline triage report, this happened on Staging, Canary and gitlab.com #335007 (closed) & #335006 (closed) (and perhaps more). But I think these test projects are now cleaned up.
What is the current bug behavior?
Sometimes pipeline status will stuck at pending, only a page refresh will update it even when I set the test to wait for 180 seconds (by default it waits for 60 seconds).
What is the expected correct behavior?
Pipeline status should update automatically without needing a page refresh.
Relevant logs and/or screenshots
Pipeline status stuck at pending
While the job actually succeeded (pipeline status should be updated)
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)