Login breaks from 16.8.2 -> 16.8.3

Please help fill in this template with all the details to help others help you more efficiently. Use formatting blocks for code, config, logs and ensure to remove sensitive data.

Problem to solve

I’m attempting to bring an outdated installation up to the current version. I went through the steps to upgrade (I’m using rpm packages) to 17.0.1. At this point I was no longer able to log in.

Log messages really aren’t very helpful.

{“severity”:“INFO”,“time”:“2024-05-29T03:19:51.234Z”,“correlation_id”:“01HZ15RXQBPDYG1AQY9X2MYN12”,“meta.caller_id”:“SessionsController#new”,“meta.remote_ip”:“192.168.10.131”,“meta.feature_category”:“system_access”,“meta.client_id”:“ip/192.168.10.131”,“message”:“Failed Login: username=myuser ip=192.168.10.131”}

Steps to reproduce

I restored from backup back to the original version, 16.8.1 and I was able to log in again. I’ve narrowed the issue down to something between 16.8.2 and 16.8.3. Upgrading to 16.8.2 has no issue, 16.8.3, I’m no longer able to log in, downgrade to 16.8.2, log in works again.

Configuration

No configuration changes are being done from a working version to a broken version. All I’m doing is dnf -y update gitlab-ce-16.8.3. Verifying that it breaks, I do dnf -y downgrade gitlab-ce-16.8.2 and I can log in again.

Versions

Working versions 16.8.{1,2}
Login breaks as soon as I upgrade to 16.8.3.

• Self-managed

Is this all users or a single user?

I ran in to an issue long ago where a particular user could not login when MFA was enabled, and we tracked it down to corruption in that users profile… I think we may have not allowed all of the migration processes to run completely some time before and this was the result.

I would consider creating a fresh new admin user before the upgrade and see if that user works after the migration.

So it looks like this was somehow related to identities and ldap for the user profile. Using your suggestion, I created a new user and was able to log in. This is when I found the identity entry under my user’s profile. Comparing this to another gitlab installation, I noticed this was unique to this particular instance. I deleted the identity, which allowed me to log in again under the newer version.