[DRE-maint] Bug#915136: Test are working

David López Zajara (Er_Maqui) er_maqui at darkbolt.net
Wed Dec 12 23:09:23 GMT 2018


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

I've created a VM with debian-unstable and do a clean install.

After it, I've moved repositories, uploads, ssh keys, and database.

A difference between my installation and the test installation: On the test
installation (let's call it git-test) database are owned by postgresql
user, and on my original installation (let's call git), database is owned
by gitlab user.

I've tested accessing the git-test web. It's working OK.

I've try to move /var/lib/gitlab to /home/gitlab and I've placed a symlink
on their place. I didn't change any config for doing it. After restart
gitlab all is working OK.

gitlab:check also do all OK.

I've diffed the /etc/gitlab of git-test and /etc/gitlab of git. There's the
result:

(/etc/gitlab folder are "git" and gitlab one are "git-test")
kanade:~# diff /etc/gitlab gitlab
Common subdirectories: /etc/gitlab/environments and gitlab/environments
diff /etc/gitlab/gitlab-debian.conf gitlab/gitlab-debian.conf
9,10c9,10
< GITLAB_HOST="git.example.net"
< GITLAB_EMAIL_FROM="no-reply at git.example.net"
- ---
> GITLAB_HOST="git-test.example.net"
> GITLAB_EMAIL_FROM="no-reply at git-test.example.net"
12,15c12,14
< GITLAB_EMAIL_REPLY_TO="no-reply at git.example.net"
< GITLAB_HTTPS="true"
< gitlab_letsencrypt="true"
< gitlab_letsencrypt_email="domains at example.net"
- ---
> GITLAB_EMAIL_REPLY_TO="no-reply at git-test.example.net"
> GITLAB_HTTPS="false"
> gitlab_letsencrypt="false"
diff /etc/gitlab/gitlab.yml gitlab/gitlab.yml
35,36c35,36
<     port: 443 # Set to 443 if using HTTPS, see
installation.md#using-https for additional HTTPS configuration details
<     https: true # Set to true if using HTTPS, see
installation.md#using-https for additional HTTPS configuration details
- ---
>     #port: 80 # Set to 443 if using HTTPS, see
installation.md#using-https for additional HTTPS configuration details
>     https: false # Set to true if using HTTPS, see
installation.md#using-https for additional HTTPS configuration details
62,63c62
< #    user_home: /var/lib/gitlab
<     user_home: /home/gitlab
- ---
>     user_home: /var/lib/gitlab
164c163
<     https: true # Set to true if you serve the pages with HTTPS
- ---
>     https: false # Set to true if you serve the pages with HTTPS
511,512c510
< #        path: /var/lib/gitlab/repositories/
<         path: /home/gitlab/repositories/
- ---
>         path: /var/lib/gitlab/repositories/
Common subdirectories: /etc/gitlab/initializers and gitlab/initializers
Common subdirectories: /etc/gitlab/locales and gitlab/locales
Common subdirectories: /etc/gitlab/prometheus and gitlab/prometheus
Common subdirectories: /etc/gitlab/routes and gitlab/routes
Only in /etc/gitlab: ssl
kanade:~#

I've leaved the git installation untouched for if you need to do more
tests. Now, I know if I do a clean reinstall will be working, but I think
we need to check it and find the problem.

@praveen, if you suggest me to do the reinstall and close the bug, I'll do
it. Or maybe we can do another test, or move the failing machine to a VM
for further testing. I don't know. But I see clear the problem are: or a
problem from OS (maybe some old ruby gems installed on machine?) or a
problem on gitlab, generated by itself by using it.

I can do comparisions of "anything" you need. Please let me know how to
proceed now.


Thanks,

https://maqui.darkbolt.net/
Linux registered user ~#363219
PGP keys avaiables at KeyServ. ID: 0x4233E9F2
Los hombres somos esclavos de la historia
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEYf0F71OtDykDsKZdCU2zE9sy6H8FAlwRlQsACgkQCU2zE9sy
6H+XdQ//fh44Fi+ALctCVnvDYUUanUpSxebGJZiJrR5Han7ejGywkqlJfmS1Zy/F
RoRcgjF4Tn9Bh+wqOA+eFQWqjI2tUNVgnc3+XFvug9KeGl8rPLzbj8HpPDRfolS1
z01ejOq+d+wO5CzEJE1wyScDSkw9W0HgjHg7zUF053LJIl0hwgMt37m2UzPsiUzm
CO7pzZet3mUIWGFCnkxRgyML+fUlylts+emGdbRGO2uwWfxrIIPT2GhR+t4O89MX
XwTvLvagmcAUiipPqzHujVOyIyrpf4HfAQQOS0m1D0tLY/y6JkJLtQA1rcfBSwUf
xW31VcJqqvxGrJ3irdU6GobwLoRJawH3ZTDzo/l5+bmxx5Btxo5aZ62oA9r+E5c8
0rFe0wIQuKS2OSzUa4QyYTFqWA+FwmhRKpZEnEHb7wBJbNgcgIPdWj37JVucADcX
ETJKRBRjKspvcdU5fHD/yIW9MW0SvT2JG7u80CH8hEU6JtkHg4o7G9TIOTkzBWao
hwYj7aRYcJvQmfQUxd/9sipj5SYe48j2ws/qUtkGMx+RYLyFL0b6CVIWkAgCjtKe
Kpo4Gplivs1kQH5fQsgwk+OlBzvzw0X4yOQE4P3LtiXQTQYDV4QYdcmKixG7s9/7
hkTHGbpf0NgJn1QyDumR2Qe9K+5ZxnvEQX9C4zCjqmmB2672teM=
=gBtW
-----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20181213/0ea16346/attachment.html>


More information about the Pkg-ruby-extras-maintainers mailing list