Skip to content
GitLab
Next

500 Error accessing pipelines per project after restoring backup

Summary

Upon restoring a full Gitlab 8.17.3 backup onto a new, clean install of Ubuntu 16.04.1 I am having issues accessing anything related to pipelines/runners if the project has previously had any CI variables set or runners assigned.

Steps to reproduce

I've never experienced this issue before and haven't seen anyone with similar issues.

I believe this happens when a project has runners/variables assigned to it as the projects that haven't had any pipelines/builds ran I am able to access perfectly.

What is the current bug behavior?

I am not able to access pipeline settings on a project which has previously had pipelines/builds/variables configured before taking the backup.

Though, I can edit pipeline settings perfectly fine on projects that have never had any CI variables / runners or builds setup pre-backup.

What is the expected correct behavior?

Should be able to access these settings to change the runner options and allow builds on the project.

Relevant logs and/or screenshots

production.log

root@code:/var/log/gitlab/gitlab-rails# tail -f production.log 
Started POST "/ci/api/v1/builds/register.json" for 127.0.0.1 at 2017-03-13 16:01:33 +0000
Started POST "/ci/api/v1/builds/register.json" for 127.0.0.1 at 2017-03-13 16:01:36 +0000
Started POST "/ci/api/v1/builds/register.json" for 127.0.0.1 at 2017-03-13 16:01:39 +0000
Started POST "/ci/api/v1/builds/register.json" for 127.0.0.1 at 2017-03-13 16:01:42 +0000
Started POST "/ci/api/v1/builds/register.json" for 127.0.0.1 at 2017-03-13 16:01:45 +0000
Started POST "/ci/api/v1/builds/register.json" for 127.0.0.1 at 2017-03-13 16:01:48 +0000
Started POST "/ci/api/v1/builds/register.json" for 127.0.0.1 at 2017-03-13 16:01:51 +0000
Started POST "/ci/api/v1/builds/register.json" for 127.0.0.1 at 2017-03-13 16:01:54 +0000
Started POST "/ci/api/v1/builds/register.json" for 127.0.0.1 at 2017-03-13 16:01:57 +0000
Started POST "/ci/api/v1/builds/register.json" for 127.0.0.1 at 2017-03-13 16:02:00 +0000
Started POST "/ci/api/v1/builds/register.json" for 127.0.0.1 at 2017-03-13 16:02:03 +0000
Started POST "/ci/api/v1/builds/register.json" for 127.0.0.1 at 2017-03-13 16:02:06 +0000
Started POST "/ci/api/v1/builds/register.json" for 127.0.0.1 at 2017-03-13 16:02:09 +0000
Started GET "/go-green/sid/settings/ci_cd" for 10.0.10.178 at 2017-03-13 16:02:10 +0000
Processing by Projects::Settings::CiCdController#show as HTML
  Parameters: {"namespace_id"=>"go-green", "project_id"=>"sid"}
Completed 500 Internal Server Error in 339ms (ActiveRecord: 55.5ms)

ActionView::Template::Error (bad decrypt):
    13:         - if variable.id?
    14:           %tr
    15:             %td.variable-key= variable.key
    16:             %td.variable-value{ "data-value" => variable.value }******
    17:             %td
    18:               = link_to namespace_project_variable_path(@project.namespace, @project, variable), class: "btn btn-transparent btn-variable-edit" do
    19:                 %span.sr-only
  app/views/projects/variables/_table.html.haml:16:in `block in _app_views_projects_variables__table_html_haml___2556767703463099835_70187364551840'
  app/views/projects/variables/_table.html.haml:12:in `_app_views_projects_variables__table_html_haml___2556767703463099835_70187364551840'
  app/views/projects/variables/_index.html.haml:15:in `_app_views_projects_variables__index_html_haml___2825280730507713268_70187364827140'
  app/views/projects/settings/ci_cd/show.html.haml:4:in `_app_views_projects_settings_ci_cd_show_html_haml__4098122022041223395_70187298099620'
  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'


Started POST "/ci/api/v1/builds/register.json" for 127.0.0.1 at 2017-03-13 16:02:12 +0000

Results of GitLab environment info

System information
System:		Ubuntu 16.04
Current User:	git
Using RVM:	no
Ruby Version:	2.3.3p222
Gem Version:	2.6.6
Bundler Version:1.13.7
Rake Version:	10.5.0
Redis Version:	3.2.5
Sidekiq Version:4.2.7

GitLab information
Version:	8.17.3
Revision:	f0c970e
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
URL:		http://code.gogreen.lan
HTTP Clone URL:	http://code.gogreen.lan/some-group/some-project.git
SSH Clone URL:	git@code.gogreen.lan:some-group/some-project.git
Using LDAP:	no
Using Omniauth:	no

GitLab Shell
Version:	4.1.1
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

Checking GitLab Shell ...

GitLab Shell version >= 4.1.1 ? ... OK (4.1.1)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ... 
3/2 ... ok
3/4 ... ok
3/5 ... ok
4/7 ... ok
2/13 ... ok
4/14 ... ok
6/15 ... ok
2/19 ... ok
10/21 ... ok
10/22 ... ok
2/23 ... ok
3/24 ... ok
2/26 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /var/opt/gitlab/.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 with autocrlf=input? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory setup correctly? ... no
  Try fixing it:
  sudo chown -R git /var/opt/gitlab/gitlab-rails/uploads
  sudo find /var/opt/gitlab/gitlab-rails/uploads -type f -exec chmod 0644 {} \;
  sudo find /var/opt/gitlab/gitlab-rails/uploads -type d -not -path /var/opt/gitlab/gitlab-rails/uploads -exec chmod 0700 {} \;
  For more information see:
  doc/install/installation.md in section "GitLab"
  Please fix the error above and rerun the checks.
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: ... 
3/2 ... yes
3/4 ... yes
3/5 ... yes
4/7 ... yes
2/13 ... yes
4/14 ... yes
6/15 ... yes
2/19 ... yes
10/21 ... yes
10/22 ... yes
2/23 ... yes
3/24 ... yes
2/26 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.1.0 ? ... yes (2.3.3)
Your git bin path is "/opt/gitlab/embedded/bin/git"
Git version >= 2.7.3 ? ... yes (2.10.2)
Active users: 6

Checking GitLab ... Finished

Possible fixes

I have tried reconfiguring, force upgrading, alsorts, checking the API per project to see if any old, assigned runners are still showing but no result.