POST /profile/gpg_keys returns HTTP 200 but has no effect

Summary

Uploading a GPG public key on gitlab.com (https://gitlab.com/profile/gpg_keys) does have no visible effect, but also does not output any error

Steps to reproduce

Example Project

This is not project related but instead user account related. Tested with my own user account on gitlab.com.

What is the current bug behavior?

The public gpg key gets uploaded, the POST /profile/gpg_keys request returns 200 OK (seen in browser's developer tools), no error is displayed, but nothing happens (gpg key does not get added to my Gitlab user account).

What is the expected correct behavior?

The public key should be associated with my gitlab.com user account and key fingerprint should be visible on the GPG page after uploading.

Relevant logs and/or screenshots

See attached screen recording of the erroneous behaviour: Adding_gpg_public_key_does_nothing_-_screen_recording

Output of checks

This bug happens on GitLab.com

Possible fixes

Until now no workaround has been found.

I also checked some other things:

  • The primary email of my Gitlab.com account is the same e-mail as in 6D17B4F9.asc.txt

  • The primary key and the subkeys are all valid until 2021

  • The key doesn't use any unusual algorithm (rsa4096 and rsa2048)

  • Content of the public key file:

    pub   rsa4096 2017-09-04 [SC] [expires: 2021-10-11]
      104D24E5B232BB5FD61519776EF7464F6D17B4F9
uid           Johannes Zweng <johannes@*********>
sub   rsa2048 2017-09-04 [S] [expires: 2021-10-11]
sub   rsa2048 2017-09-04 [E] [expires: 2021-10-11]
sub   rsa2048 2017-09-04 [A] [expires: 2021-10-11]
sub   rsa2048 2017-09-04 [A] [expired: 2018-09-04]

Possible related bugs

When researching related bugs I found #26726 (closed) but this seems different as in this issue the user gets an error message (Primary keyid can't be blank) while I don't get any error at all.

Edited by 🤖 GitLab Bot 🤖