Skip to content

Custom Grafana configuration lost after upgrade to 13.0

Summary

All custom Grafana configuration (connectors, dashboards) is lost after updating GitLab to 13.0

Steps to reproduce

  • Have a valid /var/opt/gitlab/grafana directory containing several custom dashboards in data/grafana.db using the GitLab Docker container on Gitlab 13.0.0.
  • Restart the container (executing a gitlab-ctl reconfigure)
  • Grafana now creates data.bak.DATESTAMP and creates an empty data directory containing a clean installation

Example Project

N/A

What is the current bug behavior?

Grafana creates a clean install

What is the expected correct behavior?

Grafana keeps my previous configuration

Relevant logs and/or screenshots

I haven't found relevant logs. I have tried restoring the data.bak that was created as a new data directory and restarting the container, but the same thing happened again (and a new data.bak.DATESTAMP directory was created)

Output of checks

N/A

Results of GitLab environment info

Expand for output related to GitLab environment info

System information
System:
Current User:   git
Using RVM:      no
Ruby Version:   2.6.6p146
Gem Version:    2.7.10
Bundler Version:1.17.3
Rake Version:   12.3.3
Redis Version:  5.0.9
Git Version:    2.26.2
Sidekiq Version:5.2.7
Go Version:     unknown

GitLab information
Version:        13.0.0
Revision:       6743e883eae
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     11.7
URL:            https://REDACTED
HTTP Clone URL: https://REDACTED/some-group/some-project.git
SSH Clone URL:  git@REDACTED:some-group/some-project.git
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers: google_oauth2

GitLab Shell
Version:        13.2.0
Repository storage paths:
- default:      /var/opt/gitlab/git-data/repositories
GitLab Shell path:              /opt/gitlab/embedded/service/gitlab-shell
Git:            /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check

Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 13.2.0 ? ... OK (13.2.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Checking Reply by email ...

IMAP server credentials are correct? ... yes Init.d configured correctly? ... skipped MailRoom running? ... skipped

Checking Reply by email ... Finished

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab App ...

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: ... 3/1 ... yes 2/2 ... yes 3/3 ... yes 3/4 ... yes 2/5 ... yes 2/6 ... yes 3/7 ... yes 3/8 ... yes 3/9 ... yes 3/12 ... yes 3/13 ... yes 3/14 ... yes 3/15 ... yes 3/16 ... yes 3/17 ... yes 2/18 ... yes 2/19 ... yes 2/20 ... yes 2/21 ... yes 3/22 ... yes 3/23 ... yes 2/24 ... yes 8/25 ... yes 2/26 ... yes 9/27 ... yes 9/28 ... yes 9/29 ... yes 1/30 ... yes 3/32 ... yes 4/33 ... yes 4/34 ... yes 2/35 ... yes 2/36 ... yes 3/41 ... yes 3/42 ... yes 12/46 ... yes 3/47 ... yes 5/48 ... yes 2/49 ... yes 2/50 ... yes 16/51 ... yes 17/52 ... yes 16/53 ... yes 16/55 ... yes 31/56 ... yes 31/57 ... yes 12/58 ... yes 16/59 ... yes 22/60 ... yes 22/61 ... yes 7/62 ... yes 3/63 ... yes 3/64 ... yes 3/65 ... yes 24/66 ... yes 25/67 ... yes 25/69 ... yes 7/70 ... yes 1/71 ... yes 24/72 ... yes 5/74 ... yes 20/75 ... yes 3/77 ... yes 3/79 ... yes 24/80 ... yes 2/81 ... yes 3/82 ... yes 16/83 ... yes 16/84 ... yes 20/85 ... yes 3/86 ... yes 19/87 ... yes 16/88 ... yes 3/89 ... yes 3/90 ... yes 3/91 ... yes 27/92 ... yes 27/93 ... yes 3/94 ... yes 24/95 ... yes 27/96 ... yes 27/97 ... yes 3/99 ... yes 9/101 ... yes 1/102 ... yes 24/103 ... yes 3/104 ... yes 29/105 ... yes 8/106 ... yes 24/107 ... yes 24/108 ... yes 32/109 ... yes 16/111 ... yes 24/112 ... yes 20/113 ... yes 20/114 ... yes 5/115 ... yes 3/118 ... yes 3/119 ... yes 3/120 ... yes 3/121 ... yes 31/122 ... yes 32/123 ... yes 3/124 ... yes 2/125 ... yes 6/126 ... yes 29/128 ... yes 24/129 ... yes 3/130 ... yes 6/131 ... yes 3/132 ... yes 3/133 ... yes 3/134 ... yes 16/135 ... yes 37/137 ... yes 37/138 ... yes 3/140 ... yes 16/142 ... yes 24/143 ... yes 27/144 ... yes 24/145 ... yes 3/146 ... yes 16/147 ... yes 16/148 ... yes 5/150 ... yes 16/151 ... yes 8/152 ... yes 29/153 ... yes 3/154 ... yes 3/156 ... yes 2/157 ... yes 3/158 ... yes 16/159 ... yes 16/160 ... yes 43/161 ... yes 1/162 ... yes 1/163 ... yes 24/164 ... yes 3/167 ... yes Redis version >= 4.0.0? ... yes Ruby version >= 2.5.3 ? ... yes (2.6.6) Git version >= 2.22.0 ? ... yes (2.26.2) Git user has default SSH configuration? ... yes Active users: ... REDACTED Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... no Try fixing it: Please migrate all projects to hashed storage as legacy storage is deprecated in 13.0 and support will be removed in 14.0. For more information see: doc/administration/repository_storage_types.md

Checking GitLab App ... Finished

Checking GitLab subtasks ... Finished

Possible fixes

N/A