My GitLab CE installation has been working just fine. But now when I create the GitLab repo, and then follow the new repo’s ‘Command line instructions’ to ‘upload’ my existing git repo as such:
cd project git init git remote add origin email@example.com:group/project.git git add . git commit -m "initial project commit" git push -u origin master
And then refresh the repo’s porject webpage - it does not refresh with the contents of the project. All the contents of the project folder is uploaded because I can clone this repo from GitLab and get it all back.
The only way I can refresh this page to show the actual content of the folder is to perform a
gitlab-rake cache:clear command on the server!
Details of my system is as follows:
GitLab 8.13.3 GitLab Shell 3.6.6 GitLab Workhorse 0.8.5 GitLab API v3 Git 2.7.4 Ruby 2.3.1p112 Rails 22.214.171.124 PostgreSQL 9.2.18 SELinux status: disabled Linux gitlab.server.dom 3.10.0-327.36.3.el7.x86_64 CentOS Linux release 7.2.1511 (Core)
I think this has started happening only after the kernel update for the Dirty CoW vulnerability… The other recent change was to increase the webhook timeout in gitlab.rb to 60 seconds.
Has anyone seen this and can help?