Skip to content

GitLab v15.4 - 500 Error on (first) login - race condition on firstboot #1342

@JedMeister

Description

@JedMeister

As noted by @jasper-bosch in a comment on the "GitLab v15.2/v15.3 500 error" bug (i.e. #1315), under some circumstance the v15.4 release still suffers from this issue. 😭

Unfortunately it appears that it's (still) suffering from a race condition on firstboot, so does not work reliably... 😞 Looks like we'll need to have another go at fixing this troublesome issue...

In the meantime, if you hit the dreaded "500 error" on first login, please apply this workaround from the command line (if not running as root, please prefix with sudo):

gitlab-rails runner -e production "ApplicationSetting.current.reset_runners_registration_token!"

FWIW for v15.4, we moved the token resetting command to slightly later in the firstboot process (see turnkeylinux-apps/gitlab@0e9f833 ). I personally tested v15.4 prior to release and confirmed it was working for me (installed from ISO, running as a KVM guest on my server).

So we'll need to try something else now...

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions