[Bug 281668] www/gitlab-ce after upgrading to 17.4 gitlab-shell check fails

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 23 Sep 2024 15:35:35 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281668

            Bug ID: 281668
           Summary: www/gitlab-ce after upgrading to 17.4 gitlab-shell
                    check fails
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: freebsd@gbtechlab.com

The error is seen when running

    su -l git -c "cd /usr/local/www/gitlab && rake gitlab:check
RAILS_ENV=production"

-------------
error output:
GitLab Shell: ... GitLab Shell version >= 14.39.0 ? ... OK (14.39.0)
Running /usr/local/share/gitlab-shell/bin/check
gitlab-shell self-check failed
  Try fixing it:
  Make sure GitLab is running;
  Check the gitlab-shell configuration file:
  sudo -u git -H editor /usr/local/share/gitlab-shell/config.yml
  Please fix the error above and rerun the checks.

Checking GitLab Shell ... Finished

-------------
No actual error details are given, and it's just general language. However, I
noticed that

    /usr/local/share/gitlab-shell/bin/check

does not actually exist but

    /usr/local/share/gitlab-shell/bin/gitlab-shell-check

does exist.

While in the usr/local/share/gitlab-shell/bin directory, I ran:

    "ln -s gitlab-shell-check check"

to create a symbolic link to test and it seem to pass now.

-------------
Output with sumbolic link:
Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 14.39.0 ? ... OK (14.39.0)
Running /usr/local/share/gitlab-shell/bin/check
Internal API available: OK
Redis available via internal API: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

-------------
I'm not sure if this will get overwritten, or what may have changed, causing
the error.

-- 
You are receiving this mail because:
You are the assignee for the bug.