One user's commits are associated to a different user's account
Summary
In gitlab CI/CD pipelines, commits from user A appear under user B's account. Also, user B's activity, is populated by SOME of user A's commits.
Steps to reproduce
- Logging in Gitlab Community using LDAP.
- User A commits changes, and pushes to origin.
- Pipeline starts under user B's account.
- GITLAB_USER_LOGIN variable displays correct username.
What is the current bug behavior?
We see the wrong user account, associated with another user's commits.
What is the expected correct behavior?
User's A commits shall be associated with user's A account.
Relevant logs and/or screenshots
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Current User: git Using RVM: no Ruby Version: 2.3.7p456 Gem Version: 2.6.14 Bundler Version:1.13.7 Rake Version: 12.3.1 Redis Version: 3.2.11 Git Version: 2.16.4 Sidekiq Version:5.0.5 Go Version: unknown
GitLab information Version: 10.8.4 Revision: 2268d0c Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql URL: https://gitlab.company.eu HTTP Clone URL: https://gitlab.company.eu/some-group/some-project.git SSH Clone URL: git@gitlab.company.eu:some-group/some-project.git Using LDAP: yes Using Omniauth: no
GitLab Shell Version: 7.1.2 Repository storage paths: default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
Checking GitLab Shell ...
GitLab Shell version >= 7.1.2 ? ... OK (7.1.2) 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: ... 6/13 ... ok 6/16 ... ok 6/17 ... ok 6/18 ... ok 6/19 ... ok 6/21 ... ok 6/23 ... ok 6/24 ... ok 6/25 ... ok 3/26 ... ok 6/27 ... ok 13/34 ... ok 6/35 ... ok 13/36 ... ok 6/38 ... ok 49/39 ... ok 52/40 ... ok 73/42 ... ok 29/43 ... ok 71/44 ... ok 73/45 ... ok 73/47 ... ok 73/49 ... ok 71/50 ... ok 6/51 ... ok 73/52 ... ok 65/53 ... ok 125/54 ... ok 71/55 ... ok 52/59 ... ok 71/60 ... repository is empty 65/62 ... ok 76/63 ... ok 72/64 ... ok 34/66 ... ok 6/68 ... ok 85/69 ... ok 65/71 ... ok 90/72 ... ok 6/76 ... ok 87/77 ... ok 84/84 ... ok 84/85 ... ok 85/86 ... ok 6/89 ... ok 6/90 ... ok 6/91 ... ok 28/92 ... ok 87/93 ... ok 3/95 ... ok 87/99 ... ok 81/100 ... ok 3/101 ... ok 97/104 ... ok 104/105 ... ok 87/106 ... ok 85/107 ... ok 111/109 ... ok 3/110 ... ok 75/111 ... ok 117/112 ... ok 117/113 ... ok 121/116 ... ok 121/117 ... ok 121/118 ... ok 122/119 ... ok 121/120 ... ok 123/121 ... ok 123/122 ... ok 124/123 ... ok 124/124 ... ok 126/125 ... ok 104/126 ... ok 130/127 ... ok 97/128 ... ok 113/129 ... ok 18/130 ... ok 6/131 ... ok 111/132 ... ok 45/133 ... ok 110/134 ... ok 111/135 ... ok 6/136 ... ok 87/137 ... ok 87/138 ... 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 ...
Server: ldapmain LDAP authentication... Success LDAP users with access to your GitLab server (only showing the first 100 results)
USERS HERE
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? ... yes 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: ... 6/13 ... yes 6/16 ... yes 6/17 ... yes 6/18 ... yes 6/19 ... yes 6/21 ... yes 6/23 ... yes 6/24 ... yes 6/25 ... yes 3/26 ... yes 6/27 ... yes 13/34 ... yes 6/35 ... yes 13/36 ... yes 6/38 ... yes 49/39 ... yes 52/40 ... yes 73/42 ... yes 29/43 ... yes 71/44 ... yes 73/45 ... yes 73/47 ... yes 73/49 ... yes 71/50 ... yes 6/51 ... yes 73/52 ... yes 65/53 ... yes 125/54 ... yes 71/55 ... yes 52/59 ... yes 71/60 ... yes 65/62 ... yes 76/63 ... yes 72/64 ... yes 34/66 ... yes 6/68 ... yes 85/69 ... yes 65/71 ... yes 90/72 ... yes 6/76 ... yes 87/77 ... yes 84/84 ... yes 84/85 ... yes 85/86 ... yes 6/89 ... yes 6/90 ... yes 6/91 ... yes 28/92 ... yes 87/93 ... yes 3/95 ... yes 87/99 ... yes 81/100 ... yes 3/101 ... yes 97/104 ... yes 104/105 ... yes 87/106 ... yes 85/107 ... yes 111/109 ... yes 3/110 ... yes 75/111 ... yes 117/112 ... yes 117/113 ... yes 121/116 ... yes 121/117 ... yes 121/118 ... yes 122/119 ... yes 121/120 ... yes 123/121 ... yes 123/122 ... yes 124/123 ... yes 124/124 ... yes 126/125 ... yes 104/126 ... yes 130/127 ... yes 97/128 ... yes 113/129 ... yes 18/130 ... yes 6/131 ... yes 111/132 ... yes 45/133 ... yes 110/134 ... yes 111/135 ... yes 6/136 ... yes 87/137 ... yes 87/138 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.5 ? ... yes (2.3.7) Git version >= 2.9.5 ? ... yes (2.16.4) Git user has default SSH configuration? ... yes Active users: ... 96
Checking GitLab ... Finished
