Parent pipeline shows as Running while Child pipeline(s) are waiting for manual action
Summary
The status of a parent pipeline shows as 'Running', while none of the child pipelines are actually running, but waiting for manual action.
Steps to reproduce
- Create a new project. Doesn't need to contain anything other than a .gitlab-ci.yml file with a single job that trigger the subproject's pipeline
- Create one or more projects within the root of the main project (essentially more repositories comprising a mono-repo). Similarly, these projects only need to contain a .gitlab-ci.yml file with (at least) a stage that is set to 'manual'
- Once the 'parent' pipeline starts running, the child pipelines will hold on their manual stages.
- The Downstream statuses will show as 'Blocked'. The triggered pipelines will display as 'Running'. The parent/top-level pipeline will show as 'Running'
Example Project
https://gitlab.com/AntonValkenberg/gitlabuibugparentchildpipelines
What is the current bug behavior?
The Downstream statuses will show as 'Blocked'. The triggered pipelines will show as 'Running'. The parent/top-level pipeline will show as 'Running'
What is the expected correct behavior?
We'd expect the triggered pipelines to show as 'Blocked', as well as the parent pipeline show as 'Blocked'.
Relevant logs and/or screenshots
This bug happens on GitLab.com