Error 422 The change you requested was rejected on login
Summary
Similar to #35447 (closed), however I have a base local gitlab install, revertted back to super basic defaults in gitlab.rb configuration (only serving up HTTP). Uncertain when, (gone through a few gitlab-ce upgrades without actually logging into the web UI..), suddenly a POST to /users/sign_in results in 422 "The change you requested was rejected on login"
Steps to reproduce
TBD greenfield reproduction ... but for my instance, simply trying to AUTH using web UI as a local admin account results in this error.
Example Project
TBD
What is the current bug behavior?
- gitlab-ctl status shows all services up
- user visits http://gitlab-URI:80
- server redirects to http://gitlab-URI/users/sign_in
- user enters LOCAL login credentials (in my case it's a local admin user to gitlab)
- page goes: POST /users/sign_in HTTP/1.1 422
What is the expected correct behavior?
successful auth (the error message hints that "I may not have access to the thing I tried to change" ... but I'm auth'ing as a local admin user, also even tried the root account, and even some bogus FOO/BAR account! all the same result
is this some convoluted way of saying "invalid user/pass"? - I doubt my primary user password is wrong however... since it's saved and I can confirm by manually typing too.
Relevant logs and/or screenshots
422
The change you requested was rejected.
Make sure you have access to the thing you tried to change.
Please contact your GitLab administrator if you think this is a mistake.
services are all up
# sudo gitlab-ctl status
run: gitaly: (pid 12534) 260s; run: log: (pid 892) 300573s
run: gitlab-monitor: (pid 12548) 260s; run: log: (pid 906) 300573s
run: gitlab-workhorse: (pid 12517) 261s; run: log: (pid 893) 300573s
run: logrotate: (pid 12558) 259s; run: log: (pid 894) 300573s
run: nginx: (pid 12564) 259s; run: log: (pid 885) 300573s
run: node-exporter: (pid 12572) 258s; run: log: (pid 886) 300573s
run: postgres-exporter: (pid 12578) 258s; run: log: (pid 896) 300573s
run: postgresql: (pid 11895) 307s; run: log: (pid 916) 300573s
run: prometheus: (pid 12586) 257s; run: log: (pid 919) 300573s
run: redis: (pid 11897) 307s; run: log: (pid 891) 300573s
run: redis-exporter: (pid 12598) 257s; run: log: (pid 897) 300573s
run: sidekiq: (pid 12609) 257s; run: log: (pid 902) 300573s
run: unicorn: (pid 12616) 256s; run: log: (pid 900) 300573s
/var/log/gitlab/nginx/gitlab_access.log shows:
1.0.0.6 - - [06/Dec/2017:22:03:20 -0500] "POST /users/sign_in HTTP/1.1" 422 2912 "http://gitlab-URI/users/sign_in" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0"
nothing from gitlab_error.log, ... also sanity checked other logs for possible AUTH failures or something else, but nothing of interest or more additional logs
/var/log/gitlab# for dir in $(ls -1 .); do echo $dir; ls -alt $dir/ | head -5; done
My configuration for gitlab is super minimal
fermulator@fermmy-git:~$ sudo egrep -v "#" /etc/gitlab/gitlab.rb
external_url 'http://gitlab-URI:80'
git_data_dirs({
"default": {
"path": "/mnt/storage/git-data"
}
})
Output of checks
n/a
Results of GitLab environment info
# gitlab-rake gitlab:env:info
System information
System: Ubuntu 14.04
Current User: git
Using RVM: no
Ruby Version: 2.3.5p376
Gem Version: 2.6.13
Bundler Version:1.13.7
Rake Version: 12.1.0
Redis Version: 3.2.5
Git Version: 2.13.6
Sidekiq Version:5.0.4
Go Version: unknown
GitLab information
Version: 10.2.3
Revision: 3141105
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: postgresql
URL: http://<GIT-URI>
HTTP Clone URL: http://<GIT-URI>/some-group/some-project.git
SSH Clone URL: git@<GIT-URI>:some-group/some-project.git
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 5.9.4
Repository storage paths:
- default: /mnt/storage/git-data/repositories
Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks
Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
# gitlab-rake gitlab:check SANITIZE=true
Checking GitLab Shell ...
GitLab Shell version >= 5.9.4 ? ... OK (5.9.4)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
2/1 ... ok
2/2 ... ok
2/3 ... ok
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Reply by email is disabled in config/gitlab.yml
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... 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)
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
2/1 ... yes
2/2 ... yes
2/3 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.3.5)
Git version >= 2.7.3 ? ... yes (2.13.6)
Git user has default SSH configuration? ... yes
Active users: ... 3
Checking GitLab ... Finished
Possible fixes
UNKNOWN