FS#50880 - [gitlab] CSS broken after v8.12 upgrade

Attached to Project: Community Packages
Opened by Cluxter (cluxter) - Saturday, 24 September 2016, 00:17 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 30 September 2016, 21:58 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

CSS might be/is broken after upgrade to v8.12.
More details here: https://gitlab.com/gitlab-org/gitlab-ce/issues/22528
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Friday, 30 September 2016, 21:58 GMT
Reason for closing:  Fixed
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 25 September 2016, 14:56 GMT
Works fine for me. Did you run

# systemctl daemon-reload
# systemctl restart gitlab-sidekiq gitlab-unicorn gitlab-workhorse ?
Comment by Cluxter (cluxter) - Sunday, 25 September 2016, 21:54 GMT
Yes a dozen of times
Comment by Cluxter (cluxter) - Thursday, 29 September 2016, 20:39 GMT
Yes a dozen of times
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 30 September 2016, 03:34 GMT
Check the resolution in the issue you linked. I'm using nginx myself so probably this is why I'm not hitting this issue. Please confirm: Are you using apache? Does the fix in the upstream issue fix the problem for you?
Comment by Cluxter (cluxter) - Friday, 30 September 2016, 20:28 GMT
I am not using Apache nor Nginx at all.

I solved the issue by changing the default systemd config file for gitlab-workhorse. The default parameter "-listenAddr" was set on 127.0.0.1:8181. I changed it to 192.168.0.1:8181 (to make it accessible to my local network + my NAT). Then I connected to 192.168.0.1:8181 which is where gitlab-workhorse was then listening, instead of 192.168.0.1 which is where gitlab-unicorn was listening. Hence, using gitlab-workhorse instead of gitlab-unicorn was the real fix. I just followed the advice of one of the dev of gitlab, which you can read on the link I posted.

I followed the Arch Wiki about Gitlab to set it up and I didn't find anything about this. I think this is something that should be documented. The Gitlab dev team wants people to use gitlab-worhorse instead of gitlab-unicorn now so we should write it down into the tutorial.
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 30 September 2016, 21:58 GMT
Yes, that stuff should be in the wiki. However, I'm closing this then since it's not a packaging problem. Please do share your knowledge in the wiki, though.

Loading...