Scheduled Pipeline page shows `There was a problem fetching the pipeline inputs`
Summary
When visiting the Pipeline Schedules page, a user may receive an error There was a problem fetching the pipeline inputs. The error seems to stem from the ciPipelineCreationInputs GraphQL query which returns Error: GraphQL error: config not found . In the customer scenario where this was discovered, there is no .gitlab-ci.yml but pipeline execution policies are enabled across all groups. However, there are some projects where a .gitlab-ci.yml does not exist and the error is not present.
Steps to reproduce
Example Project
See example in ticket (internal)
What is the current bug behavior?
User sees There was a problem fetching the pipeline inputs. when visiting the Pipeline Schedules page
What is the expected correct behavior?
User should not see an error or be provided more information on how to correct it if it is a configuration issue.
Relevant logs and/or screenshots
- Sentry (specific event)
- Kibana
- Sentry trend on the PipelineInputsForm component
Output of checks
This bug happens on GitLab.com
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)