Some of rendered HTML code points to old SVG files, which makes most of icons invisible.
Summary
This is own installed gitlab instance. Most of Web UI icons are invisible after upgrade.
Steps to reproduce
Actually I have no clue how to reproduce it. Fault occurred somewhere between 10.X and 10.7.2
Example Project
What is the current bug behavior?
Some of rendered HTML code points to old SVG files, which makes most of icons invisible.
Old SVG:
icons-f1e1e3187fbe3fe3aa42a17cb2558778f1a2ddc2a1914f0ea7ea59d27b4e425c.svg
New SVG:
icons-fe86f87a3d244c952cc0ec8d7f88c5effefcbe454d751d8449d4a1a32aaaf9a0.svg
I did not do upgrades one by one, but rather skipped some of versions.
What is the expected correct behavior?
icons should be visible
Relevant logs and/or screenshots
contents of assets dir:
root@sbserver:/opt/gitlab/embedded/service/gitlab-rails/public/assets# ls -la icon*
-rw-r--r-- 1 root root 911 Apr 25 16:35 icon_anchor-297aa9b0225eff3d6d0da74ce042a0ed5575b92aa66b7109a5e060a795b42e36.svg
-rw-r--r-- 1 root root 496 Apr 25 16:35 icon_anchor-297aa9b0225eff3d6d0da74ce042a0ed5575b92aa66b7109a5e060a795b42e36.svg.gz
-rw-r--r-- 1 root root 981 Apr 25 16:35 icon-merge-request-unmerged-4c8b2dc268fb4c0f6b39123d313344df7f874ac1fbd8521aa05b9f2b4439da28.svg
-rw-r--r-- 1 root root 355 Apr 25 16:35 icon-merge-request-unmerged-4c8b2dc268fb4c0f6b39123d313344df7f874ac1fbd8521aa05b9f2b4439da28.svg.gz
-rw-r--r-- 1 root root 2749 Apr 25 16:35 icons-f2752fc0cc78602fb62aa6fd8bd009ceebfa8d60da879f6d67fd006cbe710f8a.json
-rw-r--r-- 1 root root 1047 Apr 25 16:35 icons-f2752fc0cc78602fb62aa6fd8bd009ceebfa8d60da879f6d67fd006cbe710f8a.json.gz
-rw-r--r-- 1 root root 95467 Apr 25 16:35 icons-fe86f87a3d244c952cc0ec8d7f88c5effefcbe454d751d8449d4a1a32aaaf9a0.svg
-rw-r--r-- 1 root root 24493 Apr 25 16:35 icons-fe86f87a3d244c952cc0ec8d7f88c5effefcbe454d751d8449d4a1a32aaaf9a0.svg.gz
Output of checks
on private GitLab instance
Results of GitLab environment info
(I have masked subdomain name)
Summary:
root@sbserver:/opt/gitlab/embedded/service/gitlab-rails/public/assets# gitlab-rake gitlab:env:infoSystem information System: Debian 9.4 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: go1.7.4 linux/amd64
GitLab information Version: 10.7.2 Revision: 4628694 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql URL: https://.asuscomm.com HTTP Clone URL: https://.asuscomm.com/some-group/some-project.git SSH Clone URL: git@*******.asuscomm.com:some-group/some-project.git 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
root@sbserver:/opt/gitlab/embedded/service/gitlab-rails/public/assets# 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: ... 4/3 ... ok 4/6 ... ok 4/7 ... ok 7/11 ... repository is empty 7/12 ... repository is empty 7/13 ... repository is empty 7/14 ... repository is empty 7/15 ... repository is empty 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: ... 4/3 ... yes 4/6 ... yes 4/7 ... yes 7/11 ... yes 7/12 ... yes 7/13 ... yes 7/14 ... yes 7/15 ... 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: ... 3
Checking GitLab ... Finished
Possible fixes
As a workaround for this I did:
ln -s icons-fe86f87a3d244c952cc0ec8d7f88c5effefcbe454d751d8449d4a1a32aaaf9a0.svg icons-f1e1e3187fbe3fe3aa42a17cb2558778f1a2ddc2a1914f0ea7ea59d27b4e425c.svg
but I am affraid what else might be broken, that I am not aware of. I tried to reinstall gitlab by apt but it did not help. Is there any way to "reinstall" gitlab, while retaining alldatabase and projects?