"Could not update the new navigation preference. Please try again later." when toggling button "New Navigation"

Summary

When enabling the "new navigation" by toggling the button in the user-menu the error occurs: "Could not update the new navigation preference. Please try again later.". Afterwards the new navigation is still disabled

Steps to reproduce

  • Open User Menu
  • Button "New Navigation"

What is the current bug behavior?

  • Error Popup "Could not update the new navigation preference. Please try again later."
  • New Navigation is still disabled.
  • Created a new "blank" User, same problem. Seems to be a general error.
  • Already restartet gitlab
  • Already run gitlab-ctl reconfigure

What is the expected correct behavior?

New Navigation is enabled and there is no error

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

  • On-Premise-Install (Omnibus) on Raspberry Pi
  • Gitlab-Version v16.3.2
System information
System:         Debian 11
Current User:   git
Using RVM:      no
Ruby Version:   3.0.6p216
Gem Version:    3.4.18
Bundler Version:2.4.18
Rake Version:   13.0.6
Redis Version:  7.0.12
Sidekiq Version:6.5.7
Go Version:     unknown

GitLab information
Version:        16.3.2
Revision:       88bbc405d6b
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     13.11
URL:            https://gitlab.my.home
HTTP Clone URL: https://gitlab.my.home/some-group/some-project.git
SSH Clone URL:  git@gitlab.my.home:some-group/some-project.git
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers:

GitLab Shell
Version:        14.26.0
Repository storages:
- default:      unix:/var/opt/gitlab/gitaly/gitaly.socket
GitLab Shell path:              /opt/gitlab/embedded/service/gitlab-shell

Gitaly
- default Address:      unix:/var/opt/gitlab/gitaly/gitaly.socket
- default Version:      16.3.2
- default Git Version:  2.41.0.gl1

Results of GitLab application Check

Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 14.26.0 ? ... OK (14.26.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Internal API available: OK
Redis available via internal API: OK
gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... yes
Number of Sidekiq processes (cluster/worker) ... 1/1

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Reply by email is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab App ...

Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Cable config exists? ... yes
Resque config exists? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... skipped (no tmp uploads folder yet)
Systemd unit files or init script exist? ... skipped (omnibus-gitlab has neither init script nor systemd units)
Systemd unit files or init script up-to-date? ... skipped (omnibus-gitlab has neither init script nor systemd units)
Projects have namespace: ...
2/1 ... yes
6/3 ... yes
6/4 ... yes
6/5 ... yes
6/6 ... yes
6/7 ... yes
3/8 ... yes
3/9 ... yes
6/11 ... yes
6/12 ... yes
11/14 ... yes
11/15 ... yes
3/17 ... yes
3/18 ... yes
31/19 ... yes
33/20 ... yes
35/21 ... yes
6/22 ... yes
35/23 ... yes
35/24 ... yes
6/26 ... yes
6/27 ... yes
35/28 ... yes
49/29 ... yes
35/30 ... yes
6/31 ... yes
49/34 ... yes
49/35 ... yes
49/36 ... yes
49/37 ... yes
49/38 ... yes
Redis version >= 6.0.0? ... yes
Ruby version >= 3.0.6 ? ... yes (3.0.6)
Git user has default SSH configuration? ... yes
Active users: ... 9
Is authorized keys file accessible? ... yes
GitLab configured to store new projects in hashed storage? ... yes
All projects are in hashed storage? ... yes

Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished
Edited by Swen Benjamin Knodel