Gitlab/Gitter User Synchronisation
Summary
Minor - User account deleted on Gitlab still viewable as Gitter member. Possible Clean-up required.
Steps to reproduce
Create two gitlab users with access to the community edition. Login to gitter as each user. Delete one of the user accounts on Gitlab. You can no longer login as this deleted user on Gitter, login defaults to the user account that is still live. Access the list of members of the gitter Gitlab CE community - the deleted account is still there as part of the community but is not accessible via login.
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behaviour, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug has been fixed in a more recent version)
What is the current bug behavior?
Please see steps to reproduce.
What is the expected correct behavior?
You may still want to have that persons comments on the community chat but they should not necessarily be shown as a live community member any longer as their account cannot be accessed.
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.)
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:env:info
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
(If you can, link to the line of code that might be responsible for the problem)