pipeline_schedule page throws 500 error
Summary
The pipeline_schedule page throws an 500 error when there is at least 1 schedule existing. Navigating to https://gitlab.example.com/example/example/pipeline_schedules with one schedule created, gives the 500 error. After creating the schedule, the schedule list page instantly throws an 500 error.
Steps to reproduce
- Go to project without schedules list.
- Click the "New Schedule" button.
- Fill out schedule creation form.
- Submit schedule form.
- Get 500 error when being redirected to the schedule list page.
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behaviour, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug has been fixed in a more recent version)
What is the current bug behavior?
The pipeline schedule page throws and shows an 500 error.
What is the expected correct behavior?
The pipelines schedule page to list the schedules and not throw an 500 error.
Relevant logs and/or screenshots
Completed 500 Internal Server Error in 441ms (ActiveRecord: 62.1ms)
ActionView::Template::Error (Object must be a Date, DateTime or Time object. nil given.):
16: = s_("PipelineSchedules|None")
17: %td.next-run-cell
18: - if pipeline_schedule.active?
19: = time_ago_with_tooltip(pipeline_schedule.real_next_run)
20: - else
21: = s_("PipelineSchedules|Inactive")
22: %td
app/helpers/application_helper.rb:170:in `time_ago_with_tooltip'
app/views/projects/pipeline_schedules/_pipeline_schedule.html.haml:19:in `_app_views_projects_pipeline_schedules__pipeline_schedule_html_haml___464277905748232521_193826180'
app/views/projects/pipeline_schedules/_table.html.haml:12:in `_app_views_projects_pipeline_schedules__table_html_haml___2965284864421156078_194279920'
app/views/projects/pipeline_schedules/index.html.haml:21:in `_app_views_projects_pipeline_schedules_index_html_haml___3851867542994745103_83282720'
lib/gitlab/i18n.rb:39:in `with_locale'
lib/gitlab/i18n.rb:45:in `with_user_locale'
app/controllers/application_controller.rb:303:in `set_locale'
lib/gitlab/performance_bar/peek_performance_bar_with_rack_body.rb:16:in `call'
lib/gitlab/middleware/multipart.rb:93:in `call'
lib/gitlab/request_profiler/middleware.rb:14:in `call'
lib/gitlab/middleware/go.rb:16:in `call'
lib/gitlab/etag_caching/middleware.rb:11:in `call'
lib/gitlab/middleware/rails_queue_duration.rb:20:in `call'
lib/gitlab/metrics/rack_middleware.rb:29:in `block in call'
lib/gitlab/metrics/transaction.rb:49:in `run'
lib/gitlab/metrics/rack_middleware.rb:29:in `call'
lib/gitlab/request_context.rb:18:in `call'
Output of checks
This is a GitLab Community instance using the sameersbn Docker image.
Results of GitLab environment info
Expand for output related to GitLab environment info
# sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=productionSystem information System: Ubuntu 14.04 Current User: git Using RVM: no Ruby Version: 2.3.4p301 Gem Version: 2.5.2 Bundler Version:1.15.1 Rake Version: 10.5.0 Redis Version: 2.8.4 Git Version: 2.13.0 Sidekiq Version:5.0.0 Go Version: unknown
GitLab information Version: 9.3.5 Revision: 0c9ceb3 Directory: /home/git/gitlab DB Adapter: postgresql URL: https://gitlab.example.com HTTP Clone URL: https://gitlab.example.com/some-group/some-project.git SSH Clone URL: git@gitlab.example.com:some-group/some-project.git Using LDAP: no Using Omniauth: yes Omniauth Providers: github, twitter
GitLab Shell Version: 5.1.1 Repository storage paths:
- default: /home/git/data/repositories Hooks: /home/git/gitlab-shell/hooks Git: /usr/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
# sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true Checking GitLab Shell ...GitLab Shell version >= 5.1.1 ? ... OK (5.1.1) 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: ... 2/1 ... ok 2/2 ... ok 2/3 ... repository is empty 11/6 ... ok 11/7 ... ok 11/8 ... ok 11/9 ... ok 4/10 ... ok 4/11 ... ok 4/12 ... repository is empty 5/13 ... ok 16/14 ... ok 16/15 ... ok 16/16 ... ok 17/17 ... ok 17/18 ... ok 17/19 ... ok 17/20 ... ok 17/21 ... ok 17/22 ... ok 17/23 ... ok 17/24 ... ok 17/25 ... ok 17/26 ... ok 17/27 ... ok 17/28 ... ok 17/29 ... ok 17/30 ... ok 17/31 ... ok 17/32 ... ok 17/33 ... ok 17/34 ... ok 17/35 ... ok 17/36 ... ok 14/37 ... ok 10/42 ... ok 10/43 ... ok 17/44 ... ok Running /home/git/gitlab-shell/bin/check Check GitLab API access: OK Access to /home/git/.ssh/authorized_keys: OK Send ping to redis server: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
Reply by email is disabled in config/gitlab.yml
Checking Reply by email ... Finished
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? ... yes Init script up-to-date? ... yes Projects have namespace: ... 2/1 ... yes 2/2 ... yes 2/3 ... yes 11/6 ... yes 11/7 ... yes 11/8 ... yes 11/9 ... yes 4/10 ... yes 4/11 ... yes 4/12 ... yes 5/13 ... yes 16/14 ... yes 16/15 ... yes 16/16 ... yes 17/17 ... yes 17/18 ... yes 17/19 ... yes 17/20 ... yes 17/21 ... yes 17/22 ... yes 17/23 ... yes 17/24 ... yes 17/25 ... yes 17/26 ... yes 17/27 ... yes 17/28 ... yes 17/29 ... yes 17/30 ... yes 17/31 ... yes 17/32 ... yes 17/33 ... yes 17/34 ... yes 17/35 ... yes 17/36 ... yes 14/37 ... yes 10/42 ... yes 10/43 ... yes 17/44 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.3 ? ... yes (2.3.4) Git version >= 2.7.3 ? ... yes (2.13.0) Active users: ... 3
Checking GitLab ... Finished