Creating a new Pipeline errors: "The form contains the following error: Undefined error"
Summary
When creating a new Pipeline for a project, the web application's UI shows an error without any corresponding logs in the docker logs
stream.
Steps to reproduce
- (Probably): Make a new Environment with the same name as a branch that hasn't yet been pushed
- (Probably): Push that branch for the first time
- Go to
Projects > [project] > CI / CD > Pipelines" and click
Run Pipeline` - On the inconsistently-named
New Pipeline
page, select any branch and clickCreate Pipeline
- Observe the error
Example Project
n/a
What is the current bug behavior?
A useless red error message appears in the HTML that says:
The form contains the following error:
- Undefined error
And there are no relevant error messages showing up in the docker logs gitlab
logs.
What is the expected correct behavior?
The Pipeline should start running.
Relevant logs and/or screenshots
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
# gitlab-rake gitlab:env:infoSystem information System: Proxy: no Current User: git Using RVM: no Ruby Version: 2.3.6p384 Gem Version: 2.6.13 Bundler Version:1.13.7 Rake Version: 12.3.0 Redis Version: 3.2.11 Git Version: 2.14.3 Sidekiq Version:5.0.5 Go Version: unknown
GitLab information Version: 10.7.2-ee Revision: a4f29081 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql DB Version: 9.6.8 URL: http://${GITLAB_HOST} HTTP Clone URL: http://${GITLAB_HOST}/some-group/some-project.git SSH Clone URL: git@${GITLAB_HOST}:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: no Using Omniauth: no
GitLab Shell Version: 7.1.2 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
# gitlab-rake gitlab:check SANITIZE=true Checking GitLab Shell ...GitLab Shell version >= 7.1.2 ? ... OK (7.1.2) Repo base directory exists? default... yes Repo storage directories are symlinks? default... no Repo paths owned by git:root, or git:git? default... yes Repo paths access is drwxrws---? default... yes hooks directories in repos are links: ... 36/1 ... ok 36/2 ... ok Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Reply by email is disabled in config/gitlab.yml Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 36/1 ... yes 36/2 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.5 ? ... yes (2.3.6) Git version >= 2.9.5 ? ... yes (2.14.3) Git user has default SSH configuration? ... yes Active users: ... 4 Elasticsearch version 5.1 - 5.5? ... skipped (elasticsearch is disabled)
Checking GitLab ... Finished
Possible fixes
This issue usually accompanies this issue: https://gitlab.com/gitlab-org/gitlab-ee/issues/5864
This issue is also aggravated by the fact that Environments can't be deleted. Please implement a "Delete Environment" button like this year-old issue is suggesting: https://gitlab.com/gitlab-org/gitlab-ce/issues/25388
Print context in error messages, and always print in the log file when an error is shown by the UI in the web application.
Also, give the user the ability to delete Environments. Everything that can be created must be deletable. Make a "Delete Environment" button like this year-old issue is suggesting: https://gitlab.com/gitlab-org/gitlab-ce/issues/25388